Ishan Vohra: Improve your Android App Performance by 10X with Compose Stability
Original post Improve your Android App Performance by 10X with Compose Stability
Article Summary
Your Jetpack Compose app might be recomposing 10X more than it needs to. The culprit? Stability.
Compose's smart recomposition system only works when it can detect stable parameters. When classes are marked unstable, even unchanged data triggers unnecessary recompositions that tank your performance.
Key Takeaways
- Unstable classes force Compose to recompose even when data hasn't changed
- Use Compose Compiler reports to identify stability issues in your code
- Mark data classes with @Immutable or @Stable to enable skipping
- Collections and lambdas often break stability without you realizing it
Fixing compose stability can reduce recompositions by 10X by letting Compose skip unchanged composables.
Continue reading
PickMe
Sep 24, 2026
More from Ishan Vohra
Ship Your Compose UI Updates in Seconds
Posts on Medium
Mar 3, 2026
Also on Android
Never Miss a Critical App Crash Again: Integrating Firebase Crashlytics with Google Chat
PickMe
May 10, 2026
What This Article Covers
Android developers often can't figure out why their Compose apps recompose too often. Unstable classes quietly cause unnecessary UI updates, which slows down the app and drains the battery.
The Compose Compiler reports tool can find stability issues in your code. Once you find them, add @Immutable or @Stable annotations to your data classes so Compose can skip recomposing unchanged composables.
Fixing stability problems can cut recompositions by 10X. This lets Compose skip over composables that haven't changed, which makes apps noticeably faster.
This page summarizes “Improve your Android App Performance by 10X with Compose Stability” by Ishan Vohra, published Nov 15, 2025. All credit for the original work goes to the authors.
