compose-state-authoring

Jetpack Compose state resets on recomposition when using bare local vars instead of remembered state holders. Wrapping your state with remember and mutableStateOf ensures values persist across recompositions and correctly trigger UI updates.

To manage mutable collections in Jetpack Compose, use mutableStateListOf and mutableStateMapOf instead of standard Kotlin collections. These specialized state holders ensure that any modifications to the list or map are observed and trigger the necessary recomposition.

Use @ReadOnlyComposable in Jetpack Compose when a composable function strictly reads state without modifying it. Applying this annotation enforces a read-only contract and allows the Compose compiler to optimize the function by skipping unnecessary recompositions.

Refactor a plain var to state in Jetpack Compose by replacing it with a dedicated state holder. Apply remember alongside mutableStateOf to back the local state, ensuring the mutable value survives recomposition and properly notifies the framework of structural changes.

The best way to enforce local state contracts in Compose is to systematically apply state backing rules during code reviews. Ensure mutable state is accessed through proper state holders and verify that read-only composables are correctly annotated with @ReadOnlyComposable.