A developer has successfully moved a Kotlin Multiplatform project to production across five platforms: Web, Android, iOS, Desktop, and CLI. Using Kotlin 2.3.0 and Compose Multiplatform, the same codebase now runs on WASM, JVM, and Native targets. The author shared their coding sessions on YouTube, documenting a surprisingly positive overall experience despite encountering several unexpected hurdles.

The journey revealed specific toolchain friction points. Apple's App Store requirements proved particularly strict, rejecting the project due to unsigned binaries across the entire stack. This forced a workaround, distributing the macOS app via DMG through GitHub Releases instead. Other issues included silent failures in fastlane version injection and detekt static analysis skipping shared code unless configured with source-set-specific tasks.

Continuous integration also presented surprises. A single configuration line—using the gradle/actions/setup-gradle action—slashed build times by nearly threefold, from over six minutes to just two. The author concludes that while edge cases exist, the KMP tooling is mature enough for production. The key takeaway for developers is that shared code can now reliably ship across platforms, provided you navigate these specific platform quirks.