compose-side-effects

Use LaunchedEffect for suspending, deferred, or keyed one-shot work such as collecting a Flow. Use DisposableEffect when you register a listener, callback, or resource that needs a matching onDispose cleanup.

Use rememberUpdatedState when a long-running effect must not restart but should invoke the latest callback, such as a timeout calling onTimeout. Do not use it to avoid proper keys, and never read its delegate eagerly inside a remember block.

LaunchedEffect(Unit) never restarts, so it keeps capturing the first value of any changing parameter like a userId. Key the effect by the changing value, for example LaunchedEffect(userId), so the work restarts with fresh input.

Collect event Flows such as snackbar or navigation events inside LaunchedEffect with a proper key. For UI render state, use collectAsStateWithLifecycle near the state holder and pass plain values into the UI composable.

Yes, use rememberCoroutineScope and call scope.launch inside the onClick callback for suspending work like showing a snackbar. Avoid setting an event flag in state just to trigger a LaunchedEffect.

snapshotFlow only converts Compose snapshot reads into a Flow; the Flow is cold and inert until a terminal operator runs. You must call collect inside a LaunchedEffect for emissions to be observed.