android-coroutines

Prevent coroutine memory leaks by enforcing structured concurrency with lifecycle-aware scopes like viewModelScope. This ensures background jobs are automatically cancelled when the ViewModel is destroyed, maintaining main-safety and preventing crashes.

Manage UI state streams by exposing data through StateFlow or SharedFlow within your architecture. Combine this with repeatOnLifecycle to ensure Flow collection only occurs during active lifecycle states, preventing unnecessary background processing.

Inject CoroutineDispatcher into your repositories and ViewModels rather than hardcoding it. This allows you to swap in a TestDispatcher during unit tests, enabling deterministic testing with runTest for your asynchronous programming logic.

Structured concurrency works directly with lifecycleScope to bind background processing to component lifecycles. This guarantees that coroutines launched for data loading are properly cancelled when the lifecycle owner is destroyed.

Android coroutine crashes occur when UI updates happen off the main thread. Enforce main-safety by injecting CoroutineDispatcher for background work and switching back to the main dispatcher before updating UI state streams.

Use Kotlin coroutines for lifecycle-aware data loading by applying structured concurrency across ViewModels, Repositories, and the Data layer. This standardizes asynchronous programming and ensures proper cancellation semantics throughout your app.