ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Rotation wipes Compose state held in plain remember. Hoist it to the caller and switch to rememberSaveable, and your forms, toggles, and counters survive configuration changes with no ViewModel boilerplate.
Learn how to lift UI state into a ViewModel and wrap it with rememberSaveable so composables stay pure, survive rotation, and are easier to unit test.
Learn how to keep UI state (e.g., expanded/collapsed) of list items stable while scrolling and across configuration changes using LazyColumn item keys and rememberSaveable.
Use rememberSaveable to keep Compose UI state—text, toggles, lists—through device rotations without a ViewModel. Follow the step‑by‑step guide, verify with Layout Inspector, and know the limits.
Goal Determine whether Jetpack Compose should expose a runtime budget API or compile-time guard for rememberSaveable to prevent TransactionTooLargeException when saved state surpasses the platform's IPC parcel limit. Constraints and uncertainty The Activity savedInstanceState Bundle enforces a ~50–100 KB parcel budget that varies by Android version and OEM.
android
jetpackcompose