Never Be Confused Again! A Practical Guide to Writing Jetpack Compose
summary
Covers practical Jetpack Compose rules: prefer stateless composables and unidirectional data flow (hoist state, expose events as lambdas), accept one Modifier parameter with default Modifier, and avoid wrapping children in padding components. Recommends using slot parameters only when needed and encapsulating argument logic into small classes; demos use Android Studio Layout Inspector to show skipped recompositions, a lambda-based graphicsLayer to avoid unnecessary recomposes, and suggests Runtime Lint or Slack Compose Lint for team enforcement.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 6:45Compose fundamentals
- 12:27Design patterns
- 17:24Stateless design
- 20:34Parameter best practices
- 25:54Modifier usage
- 27:59Performance optimization
- 30:03Accessibility basics
- 32:12Team rules
- 35:21Summary
related talks
38mDesigning scalable Compose APIs
42mJetpack Compose: Art of the State
33mThe dark sides of Jetpack Compose
48mLearning Jetpack Compose By Example
01h 12mJetpack Compose over inheritance
32mJetpack Compose — Next Gen Kotlin UI Toolkit for Android
21mGaining Composure
44mUnleashing the Power of Jetpack Compose: Revolutionizing Android UI Development