The D-KMP architecture: Declarative UIs + Kotlin MultiPlatform + MVI pattern
summary
Claims that a Kotlin Multiplatform core holds 85% shared business logic while UI stays platform specific (JetpackCompose, SwiftUI, Kotlin/React) so only ~15% is per-platform. Architecture uses MVI with unidirectional state, state reducers and repositories; StateFlow (released May 2020) and Coroutines drive updates so StateFlow replaces RxJava. KMP and Compose hit alpha Aug 2020; approach targets greenfield apps and recommends waiting for stable Compose/JS IR before full shipping.
AI-written summary · about
chapters (13)
- 0:00Introduction to D-KMP
- 1:54Past vs future architecture
- 4:27Three pillars overview
- 4:48Declarative UI explained
- 10:48DKMP architecture details
- 11:52Declarative UI timeline
- 16:39Jetpack Compose benefits
- 23:05Kotlin MultiPlatform timeline
- 27:06KMP vs Flutter vs React Native
- 32:11MVI pattern fundamentals
- 37:52MVI code example
- 41:43DKMP benefits summary
- 43:05Q&A session
related talks
28mArchitectures with Kotlin Multiplatform
44mThe Future of Android, Kotlin, and Everything
39mKotlin Multiplatform: The (Very) Good, The Bad & The Ugly
35mThe Art of KMP: what you need to know as a multiplatform developer
38mBuild a Multiplatform Future with Kotlin
48mBuilding Multi Platform Projects with MVI
33mGetting started with KMP
43mLevel up on Kotlin Multiplatform