Skipping Compose performance problems in one commit
summary
Claim: a whole class of Jetpack Compose recomposition problems gets fixed in one commit by marking real immutables instead of guessing. Reproduce with Layout Inspector (70+ unnecessary updates), generate a stability report with compose-compiler-report.html, then fix unstable types by adding a stability configuration file and a small wrapper/data-class equals implementation (byte[] → data class). After those two small commits the recomposition counters go to zero for unaffected nodes and the input alone updates, proving the change and the measured win.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:08Compose is awesome
- 3:56Layout Inspector
- 10:05Smart Recomposition
- 15:25Stability Reports
- 18:45Annotations
- 23:20Tools
- 25:25Wrappers
- 27:31Stability Configuration File
- 29:13Solving the problems
- 31:03Testing the solution
- 37:22Outro
related talks
40mBoosting Compose UI from Sluggish to Snappy
37mPerformance in Compose:Lessons learned from Lazy layouts
44mBoosting Compose UI from Sluggish to Snappy
35mEnhancing Jetpack Compose App Performance:Tools, Strategies and Optimizations
55mOptimising UI in Jetpack Compose
36mOptimizing Render Performance of Jetpack Compose
54mOptimizing Render Performance of Jetpack Compose
01h 08mAdopting Jetpack Compose @ Scale