After this lesson you will
- Know that strong skipping compares stable params with equals() and unstable params by identity
- Read the stability contract of Menu and explain why ImmutableList is enough for the compiler to infer stable
- Distinguish the two filter layers that block wasted recomposition: distinctUntilChanged on the Flow and skipping in the Composable
Duration8 min
DifficultyBeginner
How Do You Control Recomposition?
Why Menu can skip recomposition: stability and strong skipping.
- 01Lesson Goal
- 02Part 1: Skipping Decides Which UI Does Not Need to Redraw
- 03Part 2: The Stability Contract of Menu
- 04Part 3: One State Change Passes Two Filter Layers
- 05Checkpoint
- 06Bad Smells
- 07Cheat Sheet: @Stable and @Immutable
- 08References
- 09Key Takeaway
Topics: mobile-action-pro, compose-state
9 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: Skipping Decides Which UI Does Not Need to Redraw, … — plus 64 lessons in this course, source code and checklists.
Unlock Mobile Action ProOne-time payment — lifetime access — 7-day money-back. Already purchased? Sign in