stabilizing-compose-types

To fix unstable Jetpack Compose types, apply a three-tier strategy: restructure types with val and immutable fields, annotate with @Immutable or @Stable where appropriate, and configure stabilityConfigurationFiles for third-party types, then re-run the diagnosis.

The best way to stabilize List, Set, and Map parameters in Jetpack Compose is to use kotlinx.collections.immutable. This library provides immutable collection types that the Compose compiler recognizes as stable, preventing unnecessary recompositions.

Yes, you can stabilize third-party or Java types without modifying source code by using stabilityConfigurationFiles. This tells the Compose compiler to treat specified external classes as stable, ensuring compatibility without requiring code changes.

Use @Immutable when all properties of a type are truly immutable and cannot change after construction. Use @Stable when the type is mutable but the Compose runtime can safely treat its instances as stable across recompositions.

Yes, the three-tier stability workflow ensures compatibility with Kotlin 2.0+ and kotlinx.collections.immutable. It validates fixes by re-running the stability analysis to confirm parameters are either stable or runtime.

If you cannot make a Jetpack Compose type truly stable, use the StableHolder escape hatch provided by the workflow. This mechanism wraps unstable types, allowing them to bypass strict stability checks while you verify the overall composition behavior.