Instacart's Caper team migrates its smart-cart Android app to Jetpack Compose with AI, 5-7x faster on navigation
Instacart's Caper smart-cart Android app was built on Fragments and XML, and the move to Jetpack Compose was first scoped as a multi-quarter effort. The team split it into four phases. Phase 1 was done by hand to learn the patterns. In Phase 2 (30+ sub-navigation graphs, 130+ destinations moving to type-safe Kotlin DSL routes) they fed the AI git diffs of finished migrations, corrected it live and kept a 325+ line migration guide up to date. For Phase 3 (100+ Fragment features to pure Compose) the guide became a 17-step AI skill that captures a Paparazzi screenshot baseline, builds the Compose screen, checks visual parity, updates navigation and deletes the old Fragment, with engineers verifying screenshots. Phase 4, Compose Navigation, is under way.
The numbers (as reported)
| Phase 2 speed-up | 5-7x |
|---|---|
| Engineering hours saved | Estimated 300-350 (Phase 2) |
| Navigation scope | 30+ sub-navigation graphs, 130+ destinations |
| Fragment features to migrate | 100+ |
| Migration guide | 325+ lines, 17-step skill |
Facts
- Company / subject
- Instacart
- Tools
- Unstated
- Codebase
- brownfield
- Work type
- Migration
- Stack
- Android, Kotlin, Jetpack Compose, Paparazzi
- Published
- 2026-02-03
- Last checked
- 2026-11-06
What the source claims Practitioner (own blog/paper)
Claimed by the builder, writing about their own work. Not checked independently.
- 5-7x speed increase in Phase 2, saving an estimated 300-350 engineering hours 5-7x; 300-350 hours
“The 5–7x speed increase we observed in Phase 2 saved an estimated 300–350 engineering hours”
- AI reduced variance across migrations, improving quality and predictability
- Migrations ran in parallel with feature development without blocking it
Caveats
No coding tool or model is named. Speed-up and hours saved are estimates for Phase 2 only; Phase 3 was still in progress and Phase 4 had just started when published.
More stories by tool: Unstated
Related topics: MigrationsBrownfield codebases