Adaptive UI
Taking a live app from portrait to landscape without breaking it.
- Role
- Product Owner & Business Analyst
- Timeline
- Sep 2025 – May 2026
- Context
- Capgemini · global QSR brand
- Status
- Shipped
Problem
The client wanted landscape support in a live, portrait-only app on a fixed deadline, and estimated the job at 90 screens. Nothing could break in the markets already using it.
Outcome
My screen-by-screen analysis found 324 screens, including popups and half-sheets. All 324 were delivered across five markets on iOS and Android, with a demo to the client every sprint.
- 324screens found (estimate was 90)
- ~400user stories in 21 epics
- 28developers across time zones
- Discover
- Understand
- Define
- Ideate
- Prototype
- Build
- Launch
- Adopt
- Measure
- Improve
Discover · Understand · Define · Ideate · Build · Launch · Measure · Improve
Client work: described without screenshots, client names or confidential figures.
Before and after
The problem
The app was live in five markets and portrait-only. The client wanted landscape support on a fixed timeline, and their estimate was 90 screens. Any regression would hit real customers.
Finding the real scope
Before committing to a plan I walked through every journey on the app, screen by screen. Counting popups, half-sheets and small states as well as full screens, the real number was 324, more than three times the estimate. I documented every screen flow in Confluence so the client, market leads and developers were all looking at the same map.
What I did
- Ran requirement sessions with market leads and the client, and did impact analysis per screen and business rule so existing logic stayed untouched.
- Worked with the UI/UX team to redesign layouts for landscape, and gave developers the user journey, edge cases and error cases for each screen.
- Owned 21 epics, about 400 user stories and around 1,200 test cases for a 28-developer team spread across time zones.
- Demoed progress to the client every sprint along with the next sprint’s plan.
- Checked the work against EU accessibility and Google Play requirements, and helped developers chase down issues such as redundant API calls and memory leaks.
Outcome
All 324 screens shipped across five markets on iOS and Android without a platform rebuild. Finding the true scope early is what made the deadline believable.
Stack and tools