collecting-flows-safely

To optimize Jetpack Compose flow collection and reduce battery drain, migrate UI consumers from `collectAsState()` to `collectAsStateWithLifecycle()` and apply `.conflate()` or `.distinctUntilChanged()` to prevent unnecessary recompositions from chatty flows.

Your Compose UI experiences unnecessary recompositions from StateFlow because standard `collectAsState()` continues collecting in the background. Applying `.distinctUntilChanged()` and migrating to lifecycle-aware collection prevents these redundant UI invalidations.

The best way to collect SharedFlow without causing background battery drain is using `collectAsStateWithLifecycle()`. This lifecycle-aware approach pauses flow collection when the UI is inactive, preventing wasted resources.

To fix the Flow as composable parameter antipattern in Kotlin, hoist `Flow<T>` parameters out of composables. Collect the flow at the parent level and pass the resolved state down to prevent composition lifecycle issues.

You should apply `.conflate()` to sensor and location streams in Compose when stream emission rates exceed the UI's rendering speed. This drops intermediate values, keeping only the latest state to reduce UI invalidations.

Yes, you need knowledge of Kotlin coroutines and Jetpack Compose to use `collectAsStateWithLifecycle()`. The migration process relies on understanding coroutine flow operators and lifecycle boundaries to safely optimize UI performance.