Kotlin Multiplatform Library Development
summary
Shows a concrete approach to wrapping native SDKs by publishing a Firestore KMP wrapper that uses empty type aliases plus extension functions to avoid delegate explosion, explains why most expect/actual should be minimized and to prefer interfaces for testability, demonstrates a new iOS symbolication tool Crash reporting for Kotlin iOS only that produces Crashlytics/Bugsnag stack frames, notes the arrival of multithreaded coroutines (found and fixed a bug), and documents publishing to Maven Central and using Azure Pipelines for CI.
AI-written summary · about
chapters (20)
- 0:00Introduction to KMP libraries
- 1:16Why Kotlin Multiplatform matters
- 4:49What is Kotlin Multiplatform
- 6:58Library patterns for KMP
- 7:22Expect-actual mechanics
- 9:50Minimizing platform affinity
- 12:57FireStore SDK deep dive
- 16:52Choosing interfaces vs type aliases
- 19:02Objective-C interop challenges
- 20:28Crash reporting library launch
- 23:15Publishing and CI options
- 25:42Big blockers in KMP
- 28:34Institutional libraries gap
- 30:18Mocking and testing in KMP
- 31:41File IO and server libraries
- 32:44Architecture and reactive patterns
- 33:48Shared UI and Flutter
- 34:28Getting started and coordination
- 35:10Touch Lab’s KMP projects
- 36:56Hiring Kotlin Multiplatform engineers
related talks
36mWriting Kotlin Multiplatform libraries that your iOS teammates are gonna love
26mKotlin Multiplatform in an MVVM World
29mKMP for Mobile Developers
36mIntroducing Kotlin Multiplatform in an existing project
46mExploring the Kotlin Multiplatform Ecosystem
27mKotlin: Multi-Platform
52mIntroducing Kotlin Multiplatform in an existing project
36mKotlin Multiplatform- From “Hello World” to the Real World