diagnosing-compose-stability

You diagnose Jetpack Compose stability issues by enabling and reading the Compose Compiler Reports (classes.txt, composables.txt, composables.csv, module.json). This structured workflow identifies unstable parameters and root causes of jank, high recomposition counts, and non-skippable composables.

You need Compose compiler reports when you observe jank, high recomposition counts, or non-skippable composables in your app. The reports provide a structured approach to surface per-class and per-composable stability markers like unstable, runtime, and skippable to find the root cause.

Skippable and unstable markers in composables.txt indicate whether a composable can skip recomposition if its parameters haven't changed, or if its parameters are deemed unstable. Cross-referencing these markers with classes.txt helps pinpoint the specific unstable classes causing unwanted recompositions.

Yes, you can use Compose compiler reports to fix jank by building a release variant with the reports enabled. This generates the four canonical output files needed to trace non-skippable composables and map unstable parameters to their root causes for stabilization.

A composable might have unstable parameters even with immutable classes if the Compose compiler cannot infer stability, often marking them as runtime or unstable. Reading the classes.txt report reveals these per-class stability markers to help determine the exact root cause.