kotlin-coroutines-flows

Use coroutineScope with multiple async blocks to run suspending work concurrently, then await each result. This keeps all tasks structured under one scope so a failure cancels siblings and no coroutine leaks.

Call stateIn on the Flow with viewModelScope, SharingStarted.WhileSubscribed(5000), and an initial value. The 5-second timeout keeps the upstream active across configuration changes without restarting collection.

Use StateFlow for persistent UI state that always has a current value, and SharedFlow for one-time events like snackbars or navigation. SharedFlow avoids re-delivering stale events after configuration changes.

Dispatchers.IO is only available on JVM and Android. In KMP common code, use Dispatchers.Default or Dispatchers.Main, which exist on all platforms, or inject the IO dispatcher through dependency injection.

Wrap the Flow or StateFlow in flow.test inside a runTest block, then assert each emission with awaitItem. Turbine fails the test if unconsumed events remain, catching unexpected emissions.

GlobalScope launches coroutines with no parent, so they are never cancelled with a lifecycle and can leak work. Use viewModelScope, lifecycleScope, or an explicit coroutineScope for structured cancellation.