Effective Multiplatform Architecture
summary
Migrating the Chicago Roboto Android app to Kotlin Multiplatform converts one feature at a time and keeps UI layers native, producing thin platform apps that still work. The process emphasizes modularizing first, preferring a horizontal migration starting at the feature layer, using Kotlin coroutines and Flow, converting streams with kotlinx‑coroutines‑reactive publisher, and bridging platform implementations with a typealias expected/actual bridge plus a lightweight block subscriber on iOS that interoperates with existing Rx/LiveData tooling.
AI-written summary · about
chapters (12)
- 0:00Introduction to multiplatform
- 2:38Modularize your codebase
- 7:10Starting points for migration
- 8:37Single app to multiplatform
- 10:01Multiple apps with different architectures
- 12:30Multiple apps with similar architectures
- 13:11New feature approach
- 17:01Vertical migration strategy
- 18:45Horizontal migration strategy
- 20:32Converting feature layer to multiplatform
- 24:45Reactive streams for interop
- 31:04Summary and Q&A
related talks
46mGoing Multiplatform with Your Android App
48mEffective Multiplatform Kotlin Development
22mArchitecting a Kotlin Multiplatform App
40mKotlin Multiplatform. Make your Android App Cross-Platform
52miOS Architecture with Multiplatform
26mKotlin Multiplatform in an MVVM World
48mEffective Multiplatform Kotlin Development
41mApollo-Android: a Journey to Kotlin Multiplatform
