ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Keep non-Parcelable UI state alive across configuration changes and process death in Jetpack Compose by defining a custom Saver for rememberSaveable.
When Compose UI resets to defaults after your app is killed and relaunched, the fault usually lies in remember, missing Savers, or unwired SavedStateHandle. This guide walks through ordered diagnostics, concrete fixes, and escalation criteria.
Learn how Jetpack Compose’s rememberSaveable keeps UI state across rotations and process death, the right way to use it, and the limits that can trip you up.
Learn when to use Jetpack Compose's remember versus rememberSaveable to keep UI state across rotations, with a concrete counter example, trade‑offs, and verification steps.
Learn how to pair key-based item identity with rememberSaveable in Jetpack Compose’s LazyColumn to keep scroll position, preserve checkbox state across rotations, and cut unnecessary recompositions. Includes a working example, limits, and common pitfalls.
Learn how to use Jetpack Compose's rememberSaveable to keep UI state like text field content or custom data objects alive across screen rotations and process death, with a worked example and verification steps.
When an Android app is restored from Auto Backup, Compose UI state held by rememberSaveable is not recovered. The SavedStateRegistry that backs rememberSaveable is excluded from the backup payload, so any counter, scroll position, or form input stored this way resets to its initial value after reinstall. Persistent storage such as DataStore or SharedPreferen
jetpackcompose