What does Recomposition mean to your app?
summary
Explains what recomposition actually does: the runtime records reads in the slot table, the re-composer wakes on state snapshot changes, the composer produces a change list and the applier (UI player) batches measure/layout/draw updates. Shows concrete tools—recompose highlighter in Android Studio Electric Eel, compiler metrics JSON and a logging modifier—and practical fixes: break large composables into smaller scopes, use key composables in lazy lists, prefer reading state at the leaf, wrap frequent derived values with deriveStateOf or use modifier lambdas to avoid needless recompositions.
AI-written summary · about
chapters (8)
- 0:00Introduction to Recomposition
- 3:15Composition Phases and Layers
- 8:36State Snapshot System Explained
- 17:21What is Recomposition
- 21:36Smart Recomposition Basics
- 26:07Debugging Recomposition Tools
- 28:35Tips to Leverage Smart Recomposition
- 36:13Best Practices and Wrap-up
related talks
49mWhat does Recomposition mean to your app?
55mWhat does Recomposition mean to your app
36mUnderstanding Recomposition Performance Pitfalls
45mMastering Recomposition: Optimizing State Changes for Efficient UI
28mCompose at Scale: Stop Unnecessary Recomposition
41mDeep Dive into the Compose Compiler
34mCompose Performance: Hunting for unnecessary recompositions
42mCompose: Beyond Android development