Retrofitting Legacy Code with Jetpack Compose at Scale
summary
Monzo adopts Jetpack Compose since alpha (Oct 2020) across 200+ feature modules with a 17‑person Android team, building a custom design system from Figma and exposing Compose UIs via a lightweight Compose fragment wrapper. The claim: feature delivery speeds noticeably increase (product managers flag Android as faster), UI testing and animations become easier, and reuse improves. Gaps remain: material component parity, drag‑and‑drop and auto‑size text, and the official Compose navigation feels untyped and fragile.
AI-written summary · about
chapters (7)
- 0:00Introduction and motivation
- 7:53Why Monzo adopted Compose
- 13:37Migration strategy at scale
- 19:59Integrating with legacy UI
- 23:13Results and benefits observed
- 27:07Challenges and limitations
- 30:55Convincing teams and management
related talks
43mBranching out to Jetpack Compose
01h 08mAdopting Jetpack Compose @ Scale
01h 09mJetpack Compose for consistency of your apps' UI
44mUnleashing the Power of Jetpack Compose: Revolutionizing Android UI Development
31mDesign System 3.0 with Jetpack Compose at N26
26mCompose Beyond Material Design
35mNext Generation Android UI with Jetpack Compose
46mJetpack Compose: UI Toolkit for Android and Desktop