compose-side-effects

To prevent stale callbacks in Jetpack Compose LaunchedEffect, use `rememberUpdatedState` to keep long-running effects stable while still calling the latest callbacks without restarting the effect's lifecycle.

Use `DisposableEffect` for side effects requiring proper cleanup, like listener registration, and `LaunchedEffect` for coroutine-based work like Flow collection. Both ensure imperative Compose work runs with correct lifecycle semantics.

Jetpack Compose event Flow collection restarts unintentionally when using unstable or incorrect effect keys. Choose lifecycle-accurate keys that represent when the work should restart to prevent unintended collection triggers and duplicate execution.

To sample Compose snapshot state changes into a Flow, use the `snapshotFlow` API inside your composable. This converts snapshot reads into a Flow, allowing you to react to UI state changes with proper lifecycle management.

Yes, you can trigger navigation or snackbar events correctly inside a composable by selecting the appropriate effect API. This ensures imperative UI triggers run accurately without causing extra work or lifecycle bugs.

The best way to run analytics logging in Jetpack Compose is by using the correct effect API with stable, semantic keys. This ensures logging work executes at the right time without duplicate execution or stale callback bugs.