Branching out to Jetpack Compose
summary
Twitter for Android adopts Jetpack Compose over ~2 years, shipping features like Communities and a Compose navigation drawer and reaching 19 Compose modules out of ~300 UI modules (~1/3) with over 20 teams using it. Migration starts with a single component (button), maps Horizon design tokens to Material then copies implementations, and uses an early access → allow list → Shepherds program rollout. Tooling and infra include previews, live edit, Paparazzi + Robolectric, a text facade for tomoji emoji, and open‑source ktlint rules (≈20) enforcing hoisting, explicit deps, and immutability.
AI-written summary · about
chapters (10)
- 0:00Introduction to Jetpack Compose
- 3:15Why Twitter adopted Compose
- 8:52Early access program setup
- 11:39Allow list for controlled adoption
- 13:42Shepherds program for support
- 15:26Developer experience with Compose
- 21:25Tooling and infrastructure for Compose
- 26:38Feature parity and AndroidView interop
- 30:30Static checks and lint rules
- 41:43Testing Compose UI
related talks
42mBranching out to Jetpack Compose
34mRetrofitting Legacy Code with Jetpack Compose at Scale
26mCompose Beyond Material Design
01h 09mJetpack Compose for consistency of your apps' UI
46mJetpack Compose: UI Toolkit for Android and Desktop
01h 08mAdopting Jetpack Compose @ Scale
35mNext Generation Android UI with Jetpack Compose
39mThe journey of adopting Jetpack Compose in Babbel’s App