kotlin-coroutines-flows

Topics in the source

• Kotlin Coroutines & Flows
• When to Activate
• Structured Concurrency
• Scope Hierarchy
• Parallel Decomposition
• SupervisorScope
• Flow Patterns
• Cold Flow — One-Shot to Stream Conversion

Patterns for structured concurrency, Flow-based reactive streams, and coroutine testing in Android and Kotlin Multiplatform projects. Writing async code with Kotlin coroutines Using Flow, StateFlow, or SharedFlow for reactive data Handling concurrent operations (parallel loading, debounce, retry) Testing coroutines and Flows Managing coroutine scopes and cancellation Always use structured concurrency — never GlobalScope: Use coroutineScope + async for parallel work: Use supervisorScope when child failures should not cancel siblings: WhileSubscribed(5000) keeps the upstream active for 5 seconds after the last subscriber leaves — survives configuration changes without restarting. In KMP, use Dispatchers.Default and Dispatchers.Main (available on all platforms). Dispatchers.IO is JVM/Android only — use Dispatchers.Default on other platforms or provide via DI. Long-running loops must check for cancellation: Using GlobalScope — leaks coroutines, no structured cancellation Collecting Flows in init {} without a scope — use viewModelScope.launch Using MutableStateFlow with mutable collections — always use immutable copies: state.update { it.copy(list = it.list + newItem) } Catching Cancell

This is an excerpt. Refer to the complete source and its current requirements.