A modern programming language that makes developers happier.

kotlinlang

Hey everyone! :wave:

We’re currently *piloting Kotlin Multiplatform ~(KMM)~ (KMP)*  in our architecture and had a few questions as we explore its integration in a large modular setup:
1. We’re moving from *Moshi to Kotlinx Serialization* in the shared ~KMM~ KMP layer. Has anyone recently done this in their existing architecture? Would love to hear about any learnings or common issues faced during this transition.
2. We’re planning to create a *shared ~KMM~ KMP library* that will eventually support *200+ modules*. Has anyone implemented something at this scale? Curious to know how you managed shared dependencies, modular boundaries, and coordination between Android and iOS teams for fixes.
3. Other areas we’re actively exploring:
    ◦ Monitoring *app size, build time, and startup performance* with ~KMM~ KMP in place
    ◦ Handling *Swift interop*—especially around Objective-C exposure, exception handling, and interface/protocol differences
    ◦ *Combine framework interoperability* with Ktor networking
We’ve already gone through this <https://proandroiddev.com/kotlin-multiplatform-scalability-challenges-on-a-large-project-b3140e12da9d|solid write-up>

If anyone here is working on a similar setup—especially in *large-scale Indian consumer-facing apps*—would be great to hear about your experiences and challenges in production.

Thanks in advance! :pray:

FYI <https://blog.jetbrains.com/kotlin/2023/07/update-on-the-name-of-kotlin-multiplatform/|https://blog.jetbrains.com/kotlin/2023/07/update-on-the-name-of-kotlin-multiplatform/>

&gt; TL;DR: To resolve the long-standing issues of naming inconsistency and abbreviation confusion that have puzzled many Kotlin developers over the past two years, we are deprecating the “Kotlin Multiplatform Mobile” (KMM) product name. From now on, “Kotlin Multiplatform” (KMP) is the preferred term when referring to the Kotlin technology for sharing code across different platforms, regardless of the combination of targets being discussed.

solid write-up link is broken can you please reshare it? thank you

<@U07KU5YKVE0> I have updated the same, let me know if it doesn't work.

Related to *Swift* (through Obj-C) *interop*
Current sollution is to use SKIE for API improvement in Swift
<https://skie.touchlab.co/>
You can check compatibiltiy table as well <https://github.com/kotlin-hands-on/kotlin-swift-interopedia>

But we waiting for direct Swift interop
<https://youtrack.jetbrains.com/issue/KT-49521/Support-direct-interoperability-with-Swift>

Related to *200+ modules*
Currently it will be painfull because all of the exported KMP-modules will have single namespace in Swift
<https://youtrack.jetbrains.com/issue/KT-42248/Generate-separate-namespace-for-each-Kotlin-module-when-exporting-multiple-modules-as-a-single-binary-to-Swift-Obj-C|https://youtrack.jetbrains.com/issue/KT-42248/Generate-separate-namespace-for-each-Kotli[…]orting-multiple-modules-as-a-single-binary-to-Swift-Obj-C>

There are already some works on solving both problems.
You can even find sample <https://github.com/Kotlin/swift-export-sample>

Here are direct swift export + module names separation

Currently it's experimental and not ready for prod.