------------------------------------------
DSG Mobile Apps and eComm Website Scoping
------------------------------------------

# Participants
- Morgan - Product Manager
- Jack - Product Manager
- Venky - Engineering
- Ashley - Dir. Loyalty
- Melissa - Loyalty
- Andrew - Customer Success Director
- Amir - Labs AD
- Wael - SA Pivotal
- Taavo - Director Labs NYC
- Sean Graham - Engineering Manager
- Daemon - Director of Product Management
- Pivotal Shadow

## Context & Strategy & Challenges

### WHY
1. Stay Motivated - fitness >> engagement
- _retention tool_
- _earning points when engaging with app_
- Leverage MOVE to get them points to drive them to purchase

2. Make shopping easy (Control experience, pay, pickups)
- _Hasn't been easy to buy stuff in the app_
3. Don't want to pay full price (sales, rewards, *coupons*, discounts, points)
- _Surface coupons in the wallet > major pain_

` 2 parts of the app - LOYALTY & MOVE `

4. Passionate set of users

## Challenges
- Platform is brittle. Difficult to understand how to fix it. scalability concerns. _Fitbit is on PCF._ Migrating slowly all services to PCF. Don't know why when things go wrong.

- Difficult to build and integrate new things
- cumbersome and had to hardwire features
- Runners month

- Staffing
- Team of 6.
- Don't have enough people

- Path to Prod is less than optimal

- Lot of toil and manual work around bug fixing, maintainence tasks, manual interrupts that don't add direct value to the innovation. One off solutions.
- Technical problems that have a manual solution that has not been automated because Difficult to build on existing Platform
- Fitbit Broken Token > Fitbit not syncing > manually reset their token
- FIXED in PCF with UI > want more things like that
- Half dozen of these kind of issues
- Why did the token break ?
- Bandaiding things for a while

- No one knows how how the code works
- Frail and not scalable and requires significant manual oversight

## Goals - Objectives and Key Results

[MEDIUM] Finish the Modernization Backend Services to PCF to achieve pragmatic parity
- Address issues with scalability, performance, logging and metrics
- Instrument the app for observability
- App as a whole
- Bake in Resiliency with external dependencies
- Circuit Breakers
- Fallback Services
- reduce feature function
- Accelerate Modernization
- Build features at the same time
- Identify the right services to modernize

[LOW] Better Path To Prod
- Eliminate the manual toil and maintenance tasks
- Iterative improvements with newer features

[HIGH] Technical FEATURE Enhancements [IMMEDIATE]
- Easier to innovate and add features
- Easier to Add new view trackers
- Strava
- Samsung fitness
- Integrate another activity application
- Integrate Another fitness tracking app
- Step tracking
- Activity tracking

[MEDIUM] Externalize MOVE to the company [LONG TERM] _Dependency on Technical feature enhancements_
- Make MOVE a marketing platform
- Make it easy to do a campaign/challenge/activity
- Integrate with non-native experience

[LOW] REDESIGN the CLIENT FOR Personalization _Dependency on EVOLUTION of USER experience To drive sales_
- Personalized Experience > e.g. Shoe offer for you based on the number of miles
- Location based offers
- Utilize points for motivation
- Making app best place to locate coupons and promotions
- Learn from their Shopping Experience
- Track behavioral data

[HIGH] EVOLUTION of USER experience To drive sales
- Make Shopping EASY and EFFICIENT
- <KR> 1. Revenue goes UP
- <KR> 2. Retention goes UP
- <KR> 3. Conversion goes UP
- Provide a Native Experience
- Enable partners to drive user engagement
- Better Order tracking
- Opportunities to make it BETTER/ENRICHED than the web
- What are the places that have the most impact ?
- Better agility - faster features and enhancements
- Cannot have 6 steps to checkout
- Address Existing Pain Points - [NATIVE COMMERCE BUCKET]
- Session Management
- Back and forth between web and native
- Identity challenges
- Unified login

## Workload/ Apps

---
#### MOVE
- FitBit tracker already on PCF
- Legacy SQL Server => MySQL on Azure => MySQL Tile

Services TO Extract
1. MapMyRun Service
2. Garmin Service
- JBOSS Apps - _Pull code out_
- assume something scary
3. Help delivery of the Activity Service en route to PCF
- Delivery only

- External Integrations via
- APIs
- Fitbit _already moved_
- Under Armor _move to PCF_
- Garmin _move to PCF_
- get directly device
- Apple Health _move to PCF_
- Internal Integrations
- Consumer
- CRM


##### Migration of Data from SQLServer
- Migrate from SQL Server to Databases in MySQL
- Data is not complex - 4 Tables
- Table less than 10 columns

##### Risks
- Lack of DataTx expertise
- Code is not well understood
- QA - May need to add some test coverage

---

#### eComm
- Today - Tech Stack
- Android java
- iOS Swift
- web views (owned by product teams) - r[](https://)esponsive web pages

- TBD - Future
- Native Swift and Java code
- Leverages REST APIs from external and internal deps
- WebSphere COMMERCE APIs
- API aggregation e.g. search, loyalty, customer-info
- Legacy ESB services
- Accelerate the adoption of newer versions of the app
- Ability to do multiple deploys and rollback without affecting UX
- Future of Web views
- PDP - Swift version - UI layer fast & furious
- Call the backend APIs
- Partnership with rest of eComm team

## Risks
- Will the dependency APIs be ready ?
- ASSUMPTION - Native shopping will be high Conversion
- Delivery focus!
- Q&A - Manual. Will need automation for testing.
- APPLE!! stop hiring Pivotal devs and testers
- CI/CD needs streamlining

---

## Platform
- Deploying to PCF
- Mature Platform
- clone existing CI pipelines

## Next steps
- Discussion on Wallet
- Run PAA on the JBOSS apps

## Guidance
- Tiered proposal - (Prod Dev & AppTx Mod)
- 2nd engagement if 1st goes well
- Start January 6th
- Monday-Thur offsite

### AppTx Recommendation
- m11n is already underway.
- [10- open-ended] wks m11n effort with a 3 day Inception
- Don't need to do an ES/Boris since we already know the domains and services
- Heavy focus on Delivery. Less enablement.
- Team 3.25
- Two AppTx
- One DataTx for wks 2, 3 & 4 (3wks) and rest is AppTx