coroutines-patterns

Structured coroutines use viewModelScope to automatically cancel work when the ViewModel is destroyed. This ensures coroutines respect lifecycle boundaries and prevents memory leaks and orphaned tasks in Android apps.

StateFlow holds the latest state value and replays it to new collectors, making it ideal for UI state. SharedFlow broadcasts events without state retention, better for one-time events and multiple independent subscribers.

Use supervisorScope to isolate failures so one failed child coroutine doesn't cancel siblings, and apply exception handlers in coroutine builders. This enables robust error handling across async operations and event streams.

Yes. Compose integrates with coroutines via LaunchedEffect and lifecycle-aware scopes, letting you load data tied to composition lifecycle. Flow patterns ensure data updates and cancellation follow screen recomposition and navigation.

Flow provides structured, cancellable, composable data streams with built-in lifecycle awareness and error handling. Callbacks lack cancellation safety and require manual lifecycle management, making them prone to leaks and race conditions.

Structured concurrency isolates async work in ViewModels using viewModelScope and Flow, keeping business logic separate from UI updates. This prevents tight coupling, simplifies testing, and centralizes cancellation and error handling.