Panel Discussion Adopting Jetpack Compose @ Scale
summary
Teams start with a proof of concept and monorepo integration (using basil and buck), build component libraries first, then pilot full‑screen usage; one codebase reports 15% of new ribs are composed while another counts 20,000 XML files blocking a fast switch. Adoption relies on slack white‑glove support, blocking reviewers, lint rules and baseline profiles, and incremental experiments rather than shipping compose via a single design system. Performance regressions and API iterations force cautious rollout and repeated recompose efforts.
AI-written summary · about
chapters (9)
- 0:00Introduction to panel
- 1:13Where to start adopting Compose
- 7:52Training developers on Compose
- 13:10Removing XML and Views
- 17:03Architecture changes with Compose
- 24:25Performance challenges in Compose
- 31:23Measuring success of Compose
- 33:53Design systems with Compose
- 38:08Final thoughts and lessons learned
related talks
01h 08mAdopting Jetpack Compose @ Scale
44mUnleashing the Power of Jetpack Compose: Revolutionizing Android UI Development
31mDesigning Media Friendly Jetpack Compose Components
38metpack Compose Q&A
45mHow We Built a Design System in Jetpack Compose
01h 12mJetpack Compose — live coding declarative UI
33mBuild adaptive apps with Jetpack Compose
01h 12mJetpack Compose over inheritance