In this webinar, Touchlab's own Tadeas Kriz and JetBrains' Pamela Hill guided us through iOS development with Kotlin Multiplatform. They explored the current state of Swift/Kotlin interop and highlighted tools and resources that may make your journey easier.

To maximize your iOS developer experience with KMP, you'll want to install the best tools available and configure them appropriately. There are many options available, but this is Touchlab's preferred iOS development setup.

Virtually all native mobile teams evaluating KMP start with a library publishing model. KMP module libraries are written, versioned, and "consumed" by the apps. The classic approach is to build and publish binary dependencies. In 2024, with KMP at stable and gaining significant traction, we no longer recommend this approach. It makes an inherently imbalanced iOS developer experience worse. Share Kotlin source instead.

SKIE significantly improves the API exported from Kotlin to Swift. It is a critical tool for any iOS developer or team using KMP. This guide will walk you through the basics.

Calling Kotlin Multiplatform from Swift can be a painful experience. Kotlin engineers new to KMP rarely understand the issues. The "Bad Swift Simulation" helps Kotlin engineers "feel the pain" by replicating the experience directly in Kotlin. With that experience, understanding how to fix the situation, and why you need to, is much simpler.

KMMBridge is a Gradle plugin that publishes Kotlin Multiplatform Xcode Framework dependencies for Swift Package Manager and CocoaPods. The 1.1.0 release is a significant internal refactoring to support ongoing improvements and maintainability.

For teams piloting KMP, direct access to the Kotlin source is the best way to get started. Use GitPortal to link and sync KMP source from an external repo. In Part 1, we'll install GitPortal, set up the three source code repos, and configure CI to monitor everything.