Kotlin Multiplatform in an MVVM World
summary
Fair uses Kotlin Multiplatform to share its MVVM domain and data layers, publishing KMP artifacts as Android AARs and a single iOS XCFramework via Jenkins to S3/Maven. Constants and event logging migrate cleanly and a performance tracker using expect/actual and platform timestamp providers runs on both platforms. Native networking uses serialized byte arrays and a platform HTTP executor. Developer flow improves with local publish scripts, but protobuf export creates a 70 MB header and Swift interop needs sky and more alignment before view‑state sharing.
AI-written summary · about
chapters (12)
- 0:00Kotlin Multiplatform intro
- 1:07MVVM at Fair
- 3:15What is KMP and why
- 6:21KMP adoption challenges
- 8:09Setting up KMP modules
- 11:21KMP dev workflow
- 13:02Sharing logic with expect/actual
- 16:17Native APIs and network
- 19:03Protocol buffers on iOS
- 20:28Resources and UI in KMP
- 23:58KMP future plans
- 25:00Summary
related talks
36mIntroducing Kotlin Multiplatform in an existing project
25mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
29mKMP for Mobile Developers
32m10 myths about crossplatform mobile development with Kotlin
27mKotlin: Multi-Platform
31mKotlin Multiplatform for iOS: Myths vs Reality
23mKotlin Multiplatform Mobile in production: key takeaways from developing two cross-platform apps
36mBest Practices for Developing Amazing Kotlin Multiplatform Apps