kotlin-multiplatform

To structure Kotlin Multiplatform source sets, place shared logic in commonMain and use intermediate source sets like jvmAndroid to optimize sharing across Android, Desktop, and iOS targets. Apply correct source-set ordering and Gradle configuration to manage dependencies.

Use expect/actual patterns in Kotlin Multiplatform when abstracting platform-specific APIs for crypto, IO, and compatibility logic. Apply an abstraction decision tree to determine whether to place code in commonMain or keep it platform-specific in androidMain, jvmMain, or iosMain.

The best way to migrate shared logic into a new KMP module involves reviewing an Abstraction Decision Tree to determine source set placement, then progressively moving applicable code into commonMain while arranging cross-target dependencies and module boundaries.

Yes, Kotlin Multiplatform supports sharing code between JVM and Android targets by utilizing the jvmAndroid source set. This intermediate source set allows you to share logic between androidMain and jvmMain before diverging into platform-specific implementations.

Common pitfalls when configuring Gradle source sets for KMP include incorrect source-set ordering and improper arrangement of dependencies between source sets. Real-world strategies help avoid these issues by defining clear module boundaries and migration paths.