compose-performance-audit

To fix Jetpack Compose recomposition hotspots causing UI jank, audit your composables for unnecessary state reads and apply concrete remediations like using `remember` and stable keys to prevent excessive rebuilds.

Excessive recompositions in a Compose LazyColumn are typically caused by unstable item keys and unbounded state reads. Identifying these hotspots through a code-first review helps pinpoint memory allocation issues and guide practical improvements for smoother scrolling.

To profile Android Compose rendering and layout performance, use Layout Inspector and Perfetto to collect metrics. Instrumentation with macrobenchmarks helps validate fixes by measuring frame drops across layout and rendering paths.

You should use `remember` in Jetpack Compose to optimize performance when a composable frequently recalculates values during recomposition. Applying `remember` stores the calculation result across recompositions, reducing overhead and mitigating slow rendering.

The Compose performance audit workflow does not strictly require a Layout Inspector dump but benefits from one. Providing a target Compose snippet alongside a dump allows for more accurate root-cause analysis of rendering and layout bottlenecks.

The best way to reduce frame drops in Jetpack Compose is a structured audit workflow that combines code review of state flow with profiling diagnostics. This approach yields actionable fixes like efficient image loading and stable keys to improve smoothness.