android-coroutines

To write lifecycle-aware Kotlin coroutines on Android, use viewModelScope or lifecycleScope for structured concurrency and collect flows safely with repeatOnLifecycle to prevent memory leaks.

Structured concurrency in Android coroutines ensures every launched job is tied to a specific scope, preventing unmanaged background tasks and automatically canceling operations when their parent scope is destroyed.

Handle errors and cancellation in Kotlin Flow by applying structured concurrency patterns that enforce proper scope management, ensuring active coroutines are safely canceled when an exception occurs or the lifecycle ends.

The best way to test Android coroutines and Flow is using runTest with a TestDispatcher to control virtual time, validate cancellation behavior, and verify asynchronous data-fetching logic without flakiness.

Use callbackFlow instead of standard Flow on Android when converting callback-based asynchronous APIs into cold streams, allowing structured concurrency to manage active listener registration and safe cancellation.

Yes, dependency-injected dispatchers are required for Android coroutines to enforce structured concurrency, enabling seamless swapping of IO and Main dispatchers during testing with TestDispatcher.