compose-side-effects

Manage Jetpack Compose side effects by routing outside-world work to effect APIs like LaunchedEffect and DisposableEffect, ensuring lifecycle safety and predictable UI behavior during recompositions.

Use rememberCoroutineScope for event-driven suspending work triggered by user interactions, whereas LaunchedEffect handles side work tied directly to recomposition lifecycle state and specific state keys.

Safely collect Flows in Jetpack Compose using LaunchedEffect combined with snapshotFlow, ensuring collection respects the composition lifecycle and automatically cancels when the composition leaves.

Use rememberUpdatedState to capture stable callback references inside a LaunchedEffect, allowing state updates to flow without restarting the effect or canceling its ongoing suspending work.

DisposableEffect cleanup requires correct lifecycle keys; if the key changes or composition leaves, ensure proper registration and cleanup patterns execute to avoid leaking outside-world resources.

Yes, SideEffect runs after every successful recomposition to publish state changes to non-Compose code, making it distinct from LaunchedEffect which only runs when its keyed state changes.