kotlin-specialist

Structure coroutines and Flow for multiplatform architecture by applying structured concurrency and modular design patterns across JVM, Android, and multiplatform targets. This ensures reactive streams and state management remain consistent and null-safe.

The best way to design type-safe DSLs and sealed classes in Kotlin is to use Kotlin idioms and DSL builders. This approach enables strict type hierarchies and expressive APIs while maintaining null safety.

Yes, Kotlin Multiplatform works with Compose UI and Ktor servers. You can share multiplatform libraries and reactive streams across targets while building Android UI with Compose and backend services with Ktor.

Structured concurrency applies to Android Compose by managing coroutine lifecycles tied to Compose scopes. This prevents memory leaks and ensures Flow state management updates the UI safely and predictably.

You need Kotlin Multiplatform when sharing business logic, reactive streams, and multiplatform libraries across JVM, Android, and other targets. It enables code reuse for architecture design while maintaining platform-specific UI implementations.

Limitations when coordinating coroutines across multiplatform targets include platform-specific threading constraints and expect/actual declarations for dependencies. Careful modular design and structured concurrency mitigate these cross-platform synchronization issues.