kotlin-coroutines-flows

Structured concurrency requires launching Kotlin coroutines in specific scopes rather than global ones. This pattern ties async tasks to Android or KMP lifecycles, ensuring automatic cancellation and preventing memory leaks when views unload.

Use StateFlow for holding persistent UI state and SharedFlow for emitting one-time effects in Kotlin view models. This separation ensures UI components observe state changes reliably while handling transient events without redundant emissions.

Test Kotlin coroutine flows using Turbine to intercept and assert stream emissions deterministically. This tool allows you to validate StateFlow updates and cooperative cancellation behavior without relying on real-time dispatcher delays.

Kotlin Multiplatform supports shared coroutine dispatcher logic for parallel loading by injecting platform-specific dispatchers. This enables concurrent data fetching and repository stream composition while maintaining strict cancellation safety across targets.

Your Kotlin coroutine cancels but leaves the Flow running because the collection lacks structured concurrency scoping. Ensure the Flow is collected within a lifecycle-bound coroutine scope to enforce cooperative cancellation when the parent job aborts.