# The Architectural Evolution of Flow Collection in Jetpack Compose How Android transitioned from manual coroutine management to lifecycle-aware Compose UI state APIs. - **Source:** [ProAndroidDev - Medium](https://brifing.si/source/d9553fa9-7b72-4b9b-bc73-c6bf9a40dd5f) - **Published:** 2026-10-13 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/1a5dd958-473b-41c3-8547-b4fd484af1a7 ## The Initial Solution in Compose Jetpack Compose 1.0 introduced collectAsState in July 2021 to transform Kotlin Flows into Compose State. While it automatically triggers UI recomposition on emissions, it ignores Android lifecycle changes. Backgrounded applications continue collection as long as composition stays active, risking unnecessary background processing for expensive upstream data sources. ## Flaws in Early Manual Lifecycle Before dedicated Compose integrations, developers relied on launchWhenStarted inside coroutine scopes. This approach suspended coroutines instead of cancelling them when the lifecycle dropped below the STARTED threshold. Consequently, upstream operations often persisted needlessly in the background, consuming device resources without updating an active, visible user interface. ## The repeatOnLifecycle Improvement Lifecycle 2.4.0 introduced repeatOnLifecycle in October 2021 to resolve coroutine suspension flaws. It cancels the collection block whenever the lifecycle drops below STARTED and restarts it upon return. While execution becomes significantly safer, writing this block inside Compose screens adds substantial boilerplate for routine UI state handling. ## Direct Flow Transformation Lifecycle 2.4.0 also added the flowWithLifecycle operator as an alternative stream transformation. Developers chained it before collectAsState alongside LocalLifecycleOwner to enforce lifecycle awareness. Although more concise than repeatOnLifecycle blocks, this technique still required explicit boilerplate and mandatory initial state declarations for standard Flow objects. ## The Modern Unified Standard Lifecycle 2.6.0 resolved earlier verbosity by introducing collectAsStateWithLifecycle, stabilizing in early 2023. This single API automatically cancels background collection and maps StateFlow values directly to Compose State. It serves as the recommended default across Android Compose screens, eliminating manual lifecycle plumbing while keeping declarations clean. ## Upstream Execution Boundaries Stopping UI collection does not immediately terminate upstream data pipelines. In ViewModels using stateIn with SharingStarted.WhileSubscribed(5_000), upstream producers survive a five-second buffer after subscribers leave. If the UI returns within this specific window, upstream pipelines continue running smoothly without triggering a costly internal restart. ## Distinguishing Resets and Refreshes Developers must separate three distinct operations: UI collection resumption, upstream pipeline restarts, and actual network refreshes. Reconnecting a Room Flow merely restarts database observation rather than issuing HTTP requests. Explicit network refreshes depend entirely on underlying repository implementations rather than how Compose observes state. ## Clean Architectural Separation Modern Android architecture delegates lifecycle-aware UI observation entirely to collectAsStateWithLifecycle. ViewModels and repositories remain responsible for caching policies and upstream execution lifecycles. This strict division keeps UI declarations concise, avoids hidden background resource leaks, and makes data-fetching behavior predictable across the entire application stack. ## Sources covering this story - https://proandroiddev.com/the-evolution-of-flow-collection-in-jetpack-compose-e93416a9d52d?source=rss----c72404660798---4 — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._