I had this answer bookmarked for myself to come back to when I had a chance to compare to some of my code, and I had a further question on this, if I may bug you Zach? I am currently achieving the same thing with the following code, which works as intended:

val isScrolling by remember {
    derivedStateOf { scrollState.isScrollInProgress }
}
if (isScrolling) {
    LaunchedEffect(isScrolling) {
        // ...
    }
}

is this an okay practice? or should I be changing my code to something like the snapshotFlow example you posted above?

In that case, derivedstate scrollinprogress might make sense then?

Re: using a

snapshotFlow

vs keying a

LaunchedEffect

off the changing value, the latter requires more unnecessary recomposition than the former. If the rate of change is low, as it is for

isScrollInProgress

, that’s a negligible cost. But it’s also just more moving parts, and imo less elegant. When the value changes, you trigger a recomposition, that starts a new effect, which starts a new coroutine, which will get torn down when the value changes again. Vs with

snapshotFlow

, you start one coroutine, it runs continuously, and the only thing that happens when the state changes is a new flow emission. I’m guessing the

snapshotFlow

approach will also scale better if your logic grows in complexity.