kotlin-specialist

Structured concurrency with Kotlin coroutines and StateFlow requires scoping operations to specific lifecycles and applying safe error handling. This approach ensures scalable state management without leaking background tasks across Android or JVM targets.

The best way to share code using Kotlin Multiplatform is organizing shared common logic with expect/actual declarations. This allows platform-specific optimizations for Kotlin/Native, Android, and JVM targets while maintaining a single robust codebase.

Yes, this guidance covers end-to-end patterns for Jetpack Compose and Ktor. It provides architecture references for building reactive UI and implementing server or client networking patterns within modern scalable applications.

You configure Detekt and ktlint for Kotlin multiplatform projects by applying integrated testing strategies. This enforces static analysis and code formatting rules across your shared common code and platform-specific targets.

Yes, you can use SharedFlow for safe concurrency across JVM and Kotlin/Native targets. It provides idiomatic patterns for emitting values to multiple collectors while maintaining structured concurrency and null-safety.

Your Kotlin Multiplatform code requires expect/actual declarations because they bridge shared common code with platform-specific implementations. This mechanism allows you to call native APIs on Android, JVM, and iOS while maintaining a unified architecture.