android-coroutines-expert

Use Kotlin Coroutines in Android ViewModels via viewModelScope to ensure lifecycle safety across configuration changes. This built-in scope automatically cancels running jobs when the ViewModel is cleared, preventing memory leaks and crashes.

The best way to collect Flow in Jetpack Compose is using collectAsStateWithLifecycle. This function ensures Flow collection only occurs when the UI is active, preventing unnecessary background processing and preserving device battery life.

Test Kotlin Coroutines and Flow in Android using TestDispatcher and runTest to control virtual time. For testing Flow emissions specifically, use the Turbine library to assert sequential values and verify lifecycle-safe collection behavior.

Android Coroutines cause crashes or unresponsive UIs when blocking the Main thread or using GlobalScope. Fix this by applying correct Dispatchers, switching to IO for network or disk operations, and Default for CPU-intensive background work.

Handle side effects with LaunchedEffect in Compose by tying Coroutines execution to specific UI keys. This pattern safely manages one-time or key-based actions, ensuring jobs are properly cancelled and cleaned up when the composition leaves.

Common Kotlin Coroutines anti-patterns in Android include using GlobalScope, blocking the Main thread, and leaving exceptions unchecked. Avoid these by relying on viewModelScope, applying correct Dispatchers, and implementing robust error handling.