Building Multi Platform Projects with MVI
summary
Claims that Kotlin Multiplatform plus MVI lets most model code live in a shared common module, demonstrated by a built habit‑tracker app that actually syncs and caches state and handles optimistic updates. Uses state flow and coroutines for reactive unidirectional data flow, Ktor for HTTP, adapters to expose flows to Swift, Compose/SwiftUI/Kotlinx.html for views, Cocoapods and Koin for wiring. Finds views remain platform specific, Kotlin/JS code often gains web‑specific shims, and tooling/Gradle quirks sometimes force rollbacks.
AI-written summary · about
chapters (12)
- 0:00MVI multi-platform intro
- 5:34MVI core principles
- 11:56Habit tracker app
- 15:47KMP project structure
- 19:16Reusing common libraries
- 22:26State machines & intent validation
- 27:42Ktor REST API calls
- 28:44Android UI with MVI
- 33:15Web UI with Kotlin/JS
- 36:29iOS UI with SwiftUI
- 42:47Koin dependency injection
- 45:15Future trends & closing
related talks
35mBuilding Multi-Platform Projects with MVI Architecture
26mKotlin Multiplatform in an MVVM World
48mEffective Multiplatform Kotlin Development
22mArchitecting a Kotlin Multiplatform App
32mKotlin Multiplatform in Action
48mEffective Multiplatform Kotlin Development
28mArchitectures with Kotlin Multiplatform
33mMultiplatform Functional Architecture