kotlin-coroutines

Structured concurrency in Kotlin requires every coroutine to run within a parent scope so failures propagate correctly. This ensures child coroutines are cancelled when their parent fails, avoiding unstructured launches and GlobalScope usage.

Use StateFlow for cold Flow designs requiring a single updated state value, and SharedFlow for broadcasting multiple values to multiple collectors. Choosing between them depends on whether you need state holding or simple event emission.

Safe coroutine cancellation requires avoiding CancellationException swallowing and ensuring suspend functions cooperate with cancellation. Proper cancellation semantics prevent broken parent-child scope relationships and resource leaks.

Use Channels for producer-consumer, fan-in, or fan-out communication patterns when Flow cannot express the required complex data streams. Flow is recommended first for cold stream designs before falling back to Channel primitives.

Yes, these safe concurrency patterns apply directly to tasks involving suspend functions, Flow, and Channels in both Android and server codebases. The guidance ensures correct failure propagation and cancellation across different platforms.