compose-performance-audit

To fix Jetpack Compose jank, audit your composable code and data flow to identify excessive recompositions, then use Layout Inspector and Perfetto traces to guide root-cause analysis and apply concrete fixes like stabilizing parameters.

Excessive recompositions in Android Compose are typically caused by unstable parameters, unstable keys, or heavy work executing directly within the composition phase, requiring data flow analysis to diagnose and remediate.

You use Perfetto traces to diagnose Compose performance issues by collecting target composable code, reproduction steps, and trace data, which enables evidence-based root-cause analysis for slow rendering and jank.

Yes, Layout Inspector can detect recomposition storms in Jetpack Compose by enabling recomposition highlights to visually identify which composables are recomposing excessively and guide remediation.

The best way to optimize Compose UI performance during code review is to analyze the target composable code and data flow to spot recomposition storms and heavy work, then verify findings using macrobenchmarks and Perfetto traces.

Your Jetpack Compose layout has high complexity due to nested composables and heavy work in composition; reduce it by using remember, stabilizing parameters, and simplifying the layout hierarchy.