Jetpack Compose: Art of the State
summary
Covers concrete state patterns for Jetpack Compose: use mutableStateOf plus remember to persist across recompositions and rememberSaveable for configuration changes; prefer immutable UI models and the state hoisting pattern (pass state + callbacks, keep state at lowest common ancestor or ViewModel). Shows an Instagram-style post example where mutating a mutable field makes composables unskippable, and recommends kotlinx immutable collections. Recomposition metrics use Android Studio Layout Inspector and a Gradle composable-report to find unnecessary recompositions.
AI-written summary · about
chapters (12)
- 0:00Introduction to compose
- 1:23Declarative vs imperative
- 4:12Building UI with compose
- 5:58Developing a component
- 11:23Understanding state
- 13:32State management tools
- 17:36State hoisting pattern
- 20:43State in view models
- 23:40Compose stability
- 29:40Handling collections
- 32:14Debugging performance
- 33:36Q&A session
related talks
32mJetpack Compose — Next Gen Kotlin UI Toolkit for Android
11mInvest in Real State: A workshop for State in Compose
01h 12mJetpack Compose over inheritance
45mOn the road to Jetpack Compose
31mDesigning Media Friendly Jetpack Compose Components
44mState in Jetpack Compose
45mMastering Recomposition: Optimizing State Changes for Efficient UI
36mNever Be Confused Again! A Practical Guide to Writing Jetpack Compose