Multiplatform Functional Architecture
summary
Argues that a single, testable core can run on Android and iOS by combining Kotlin Multiplatform with a pure Model View Update (MVU) core implemented as the Ulong library; effects live at guarded ports and messages are exhaustive via sealed classes. Shows a dice-rolling app with persistent roll history, Android using Litho and an iOS SwiftUI port that’s “not quite as good,” demonstrates declarative rendering, runtime-driven state fold, and notes Kotlin Multiplatform is promising but still rough around the edges.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 3:47Inconsistency in multiplatform development
- 6:21Vision for single codebase approach
- 9:52Multiplatform functional architecture explained
- 11:58Functional programming basics
- 17:43Functional architecture and boundaries
- 19:27Unidirectional architecture patterns
- 25:57MVU as best architectural style
- 28:27Declarative UIs and purity
- 30:15Demo of dice rolling app
- 32:10Summary and Q&A
related talks
48mBuilding Multi Platform Projects with MVI
48mEffective Multiplatform Kotlin Development
26mKotlin Multiplatform in an MVVM World
48mEffective Multiplatform Kotlin Development
28mArchitectures with Kotlin Multiplatform
52miOS Architecture with Multiplatform
22mArchitecting a Kotlin Multiplatform App
36mGoing Multiplatform with Kotlin
