android-compose-state-effects

To avoid memory leaks in Android Compose state management, use lifecycle-aware functions like `collectAsStateWithLifecycle` and properly scope side effects using `DisposableEffect` to ensure resources are cleaned up when the composable leaves the composition.

The best way to handle side effects in Jetpack Compose is using dedicated effect APIs: `LaunchedEffect` for coroutine-based tasks, `DisposableEffect` for necessary cleanup, and `SideEffect` for publishing state changes to non-Compose code safely.

Use `derivedStateOf` in Compose when you need to prevent unnecessary recompositions by ensuring UI updates only occur when a calculated state crosses a specific threshold, rather than recomposing on every underlying input change.

Manage Compose state snapshots by using `snapshotFlow` to convert Compose state into a cold Flow, allowing you to observe specific state changes over time, combined with `rememberUpdatedState` to capture the latest state values within long-running effects safely.

Yes, Android Compose state management works seamlessly with lifecycle-aware components by utilizing `collectAsStateWithLifecycle` to automatically halt state collection when the app enters the background, saving battery and preventing leaks.

Your Compose UI recomposes excessively during state updates because state is not optimized; using `rememberSaveable` for UI state and `derivedStateOf` for computed values prevents redundant recompositions by caching results until inputs actually change.