compose-stability-diagnostics

Diagnose unstable Compose parameters by running compiler reports to identify unstable inputs, per-item lambda captures, and parameter churn across recompositions. Apply stability improvements using immutable collections and proper annotations to restore skippability.

Fix Compose parameter instability by applying immutable collections, adding @Immutable or @Stable annotations, and utilizing per-item remember or hoist techniques. These strategies ensure inputs compare cheaply and predictably across recompositions.

You need stability configuration for Compose parameters when recomposition counts exceed actual data changes, or when per-item lambdas recompose due to captured state. Analyze unstable and stable parameter types to determine if refactoring is required.

Kotlin 2.0 strong skipping compares unstable parameters by instance identity rather than equality. While enabled by default, it can still degrade UI performance if parameters churn, making stability diagnostics and immutable refactoring still necessary.

Prevent per-item lambda captures from triggering recomposition by implementing per-item remember or hoist techniques. This stabilizes inputs across recompositions, ensuring parameters compare predictably and improving overall UI skippability.