stabilizing-compose-types

To fix Jetpack Compose unstable types, diagnose the instability and apply a three-tier strategy: rewrite with immutable collections, use @Immutable or @Stable annotations, or add a stability configuration file.

Jetpack Compose reports stability issues when types are not stable, often due to mutable properties or unannotated third-party classes, causing unnecessary recompositions that this skill diagnoses and resolves.

The best way to stabilize third-party Java types in Jetpack Compose is to use a stability configuration file, which explicitly declares them as stable without modifying their source code.

Use @Immutable when all properties of a Kotlin type are truly immutable, and use @Stable when the type can change but emits updates to inform Compose, selecting the tier based on diagnosis results.

Yes, rewriting unstable types with kotlinx.collections.immutable provides the immutability guarantees needed to stabilize Jetpack Compose types and prevent unnecessary recompositions.

You diagnose Jetpack Compose stability problems by running the diagnostic workflow to identify unstable types, then following the documentation to stabilize them using annotations or configuration files.