How do you take a custom Artifact Manager and point it to Google Cloud Storage?This post will guide you through the process on to publish artifacts to Google Cloud using your Artifact Manager.

KMMBridge allows you to publish artifacts to some of the most popular repositories online, but what if you want to publish somewhere else? This two part post will go through how to create a custom Artifact Manager for KMMBridge that will store artifacts in Google Cloud Storage

Virtually all native mobile teams integrate Kotlin Multiplatform by publishing Xcode binaries, usually with SPM. This is generally easy to integrate, but prevented iOS developers from browsing or debugging Kotlin. Today we have fixed that situation.

KMMBridge is a tool that helps you publish iOS XCFramework binaries from Kotlin Mutliplatform. The tool has seen multiple iterations over the past few years. This version simplifies the configuration and usage of KMMBridge, with a primary focus on Swift Package Manager (SPM).

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.

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.