Lifecycle‑Aware Data Flow Collection in Android with collectAsStateWithLifecycle

The article recommends using the collectAsStateWithLifecycle API to collect data streams on Android in a lifecycle‑aware way, especially when building apps with Jetpack Compose. This approach releases resources such as Firebase queries, location updates, or database connections when they are not needed, improving device health.

collectAsStateWithLifecycle is a composable function that collects values from a Flow and exposes the latest value as a Compose State . Whenever the flow emits a new value, the State updates, triggering recomposition of any composables that read State.value .

By default the API starts and stops collection when the lifecycle reaches Lifecycle.State.STARTED . Developers can change this behavior via the minActiveState parameter.

Example usage in an AuthorRoute composable:

/* Copyright 2022 Google LLC.  
   SPDX-License-Identifier: Apache-2.0 */
@OptIn(ExperimentalLifecycleComposeApi::class)
@Composable
fun AuthorRoute(
  onBackClick: () -> Unit,
  modifier: Modifier = Modifier,
  viewModel: AuthorViewModel = hiltViewModel()
) {
  val uiState: AuthorScreenUiState by viewModel.uiState.collectAsStateWithLifecycle()

  AuthorScreen(
    authorState = uiState.authorState,
    newsState = uiState.newsState,
    modifier = modifier,
    onBackClick = onBackClick,
    onFollowClick = viewModel::followAuthorToggle,
  )
}

To use the API, add the androidx.lifecycle:lifecycle-runtime-compose dependency (currently in alpha) and annotate the composable with ExperimentalLifecycleComposeApi :

// app/build.gradle file
dependencies {
    implementation "androidx.lifecycle:lifecycle-runtime-compose:2.6.0-alpha01"
}

The implementation relies on repeatOnLifecycle , which can also be used directly in the Android view system. A manual equivalent without the helper API looks like this:

@Composable
fun AuthorRoute(...){
    val lifecycle = LocalLifecycleOwner.current.lifecycle
    val uiState by produceState
(
        initialValue = viewModel.uiState.value,
        key1 = lifecycle,
        key2 = viewModel
    ) {
        lifecycle.repeatOnLifecycle(state = STARTED) {
            viewModel.uiState.collect { value = it }
        }
    }

    AuthorScreen(...)
}

The article also explains why collectAsState alone is insufficient for Android apps: while it follows the Compose composition lifecycle, it continues collecting when the app moves to the background, preventing resource release. collectAsStateWithLifecycle stops collection according to the Android lifecycle, making it suitable for Android‑specific resource management.

Migration from collectAsState to collectAsStateWithLifecycle is straightforward, as shown in the code snippet above. Using the lifecycle‑aware API helps reduce CPU usage, network traffic, and memory consumption, which is crucial for delivering performant apps to billions of users.