When native mobile teams explore KMP, getting started is pretty easy. The difficulty emerges when they try to scale. To get the most out of KMP for your team, and for KMP as a platform to succeed, we need to make scaling easy as well.

Many developers and managers have expressed the hope that with KMP they'll finally be able to "merge" their mobile teams and "mobile developers" instead of Android and iOS developers.

Lottie and Bodymovin provide amazing animations that you can now use in your Compose Multiplatform projects.

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.

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.

Huge improvement to Kotlin Multiplatform debugging in Xcode.

Do you actually need to use SPM or Cocoapods to include KMP? You don't, and it might not be the right answer

One of the best features of Compose is its interoperability. With Compose iOS, you can interop with both UIKit and Swift UI.

Slow Kotlin Multiplatform iOS build times? Many teams are building more architectures than needed or intended. Ensure you are not wasting build time

As an Android developer, you probably already use Jetpack Compose to build UI. But did you know that with a few changes you can also build your application for other platforms, such as iOS, macOS, and the Web?