Stately and Composed
summary
Shows working Compose code (Android Studio 4.2, Jetpack Compose alpha4) tying immutable Kotlin data classes to UI with Coil image loading, LiveData via observeAsState and a simple RxJava model store with reducers. Demonstrates a product card and editable text field where changing the name updates the card instantly, and explains that Compose recomposes only the affected composables and can call functions frequently or in parallel so developers must avoid side effects and use unidirectional data flow and click listeners for safe state changes.
AI-written summary · about
chapters (13)
- 0:00Introduction and thanks
- 1:17Talk overview and goals
- 3:46Product class and immutability
- 5:29Composable functions basics
- 8:40Compose vs XML state management
- 11:29Recomposition and efficiency
- 13:57Avoiding side effects in Compose
- 16:05Unidirectional data flow explained
- 17:50LiveData and ViewModel integration
- 28:42RxJava and ModelStore approach
- 33:24Building UI components
- 36:56Connecting UI to state store
- 40:34Live demo and Q&A start
related talks
35mNext Generation Android UI with Jetpack Compose
35mDeclarative UI patterns
48mLearning Jetpack Compose By Example
56mStately and Composed
40mMaking Large Screens Easier in Compose
33mThe dark sides of Jetpack Compose
34mLearning Jetpack Compose By Example
01h 09mJetpack Compose for consistency of your apps' UI