Is there a less verbose way of writing this? ```val lifecycle = LocalLifecycleOwner.current.lifecyc...

# compose

[Colton Idle]

Is there a less verbose way of writing this?

val lifecycle = LocalLifecycleOwner.current.lifecycle
DisposableEffect(lifecycle) {
  val observer = LifecycleEventObserver { _, event ->
    if (event == Lifecycle.Event.ON_RESUME) {
      vm.doThing()
    }
  }
  lifecycle.addObserver(observer)
  onDispose { lifecycle.removeObserver(observer) }
}

[Colton Idle]

vm.doThing() launches a coroutine in this case, but in other cases where I collect a flow I just write

vm.someFlow.collectAsStateWithLifecycle()

and I'm curious if I could somehow reuse this collectAsStateWithLifecycle function that's provided to us.

[Tolriq]

You can easily extract that into a reusable code.

@Composable
fun StartOnResume(block : suspend () -> Unit) {
... your helper
}

Then where wanted just StartOnResume { vm.doThing() }

[Colton Idle]

Thanks. I didn't know if there was maybe something out of the box i was missing.

[Francesc]

there is an artifact that lest you observe a LiveData as state, similar to what you can do with `flow`s, would that work for you?

[Francesc]

https://developer.android.com/reference/kotlin/androidx/compose/runtime/livedata/package-summary

[Ian Lake]

FWIW, we're tracking adding exactly this kind of helper for triggering a side-effect when the Lifecycle changes in https://issuetracker.google.com/235529345