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

Glance at latest updates to various open source libraries published by Touchlab

This article discusses the newest version of the lifecycle-viewmodel artifact, part of the official Android Jetpack library, and how it adds support for KMP projects.