6 weeks of Compose or How a good Design System is vital in Compose
summary
Rewrote a production mobile app into Compose in 6 weeks by building a focused design system: design tokens (color interface + palette), atoms/molecules/templates, and a Kotlin-first theme exposed via composition local provider so components read tokens at runtime. Built composable input abstractions with validation and state handling, kept XML/fragment interop for slow migration, and discovered that careless patterns trigger recomposition caused performance drop, fixed with remember/launchEffect and tighter scope control.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 2:23Why design systems matter
- 10:09Design tokens and atoms
- 14:28Implementing tokens in Compose
- 18:55Molecules and complexity
- 22:44Templates and reuse
- 23:06Abstractions in Compose
- 28:19Interoperability with legacy code
- 31:07Avoiding recomposition pitfalls
- 35:45Summary and closing
related talks
26mCompose Beyond Material Design
49mImplement your own design system with Jetpack Compose
39mRe-Compose your UI: building an atomic design library
36mCoupling Compose- Interoperability in a Legacy Codebase
01h 08mAdopting Jetpack Compose @ Scale
45mHow We Built a Design System in Jetpack Compose
31mDesign System 3.0 with Jetpack Compose at N26
38mDesigning scalable Compose APIs