Kotlin Multiplatform on iOS: Real‑World Practices and Key Challenges

Kotlin Multiplatform adoption and benefits

Kotlin Multiplatform (KMP) has been used in production for years. JetBrains’ survey shows that 48.4% of KMP users achieve code‑reuse rates above 50%, and 99% are satisfied with performance, package size, and stability.

1. iOS debugging difficulties

iOS developers can debug KMP code via two approaches:

Install the Kotlin plugin for Xcode (provided by Touchlab).

Use JetBrains AppCode with the Kotlin Multiplatform Mobile plugin.

The Xcode plugin suffers from broken auto‑completion and occasional crashes across Xcode versions because it is a third‑party tool and Apple does not support Kotlin.

AppCode offers stronger refactoring features but lacks core UI‑design capabilities and is not an official Apple IDE.

Consequently, no perfect iOS debugging solution exists, making the experience cumbersome.

2. Objective‑C interoperability limits

KMP bridges to iOS through Objective‑C rather than Swift, introducing compatibility costs.

Enum incompatibility

Objective‑C enums are integer‑based, while Kotlin enums are reference types, causing type‑mismatch when mapping Swift enums to Kotlin.

Missing default parameters

Swift functions can define default parameters, e.g.:

func sample(name: String, nice: Bool = true) {
    if nice {
        print("hello \(name)!")
    } else {
        print("no, it's \(name) again..")
    }
}

Callers may omit the nice argument. Because Objective‑C does not support default parameters, KMP‑generated code cannot use them; all parameters must be passed explicitly.

3. Unsupported iOS APIs

Swift’s Codable serialization cannot be automatically generated for Kotlin classes exported via KMP, even though Kotlin offers kotlinx.serialization. Manual implementation defeats the purpose of reducing duplicate code.

4. Limited native dependency support

Kotlin/Native integrates with CocoaPods, the dominant iOS dependency manager, but it does not yet support other iOS libraries. This limitation is tracked as a feature request on YouTrack.

5. Complex concurrency model

KMP’s concurrency and memory model differ across platforms, leading to inconsistent behavior. Coroutines now provide multithreading support, but concepts such as frozen objects and immutable‑object handling add learning overhead.

6. Production readiness

JetBrains’ survey data confirms that many enterprises run KMP in production. Teams should proceed cautiously because KMP depends on many JetBrains‑controlled frameworks.

Cautious trial : start with a small module rather than a full 100% migration.

Shareable components first : identify reusable business‑logic or data‑layer components and evaluate efficiency gains.

Watch version compatibility : monitor Kotlin component stability lists and assess impact of new releases.