Kotlin Multiplatform's Cross-Platform Brilliance at Norway's National Postal Service
summary
A legacy monolith’s thousands of duplicated business rules are migrated incrementally into a shared Kotlin Multiplatform library (started 2019, POC 2021, production-ready 2023), compiled into JVM and JS artifacts with JS export/JVM static wrappers, and published to Maven and npm so frontends and backends consume the same validations. Result: ~1,000,000 automated tests, manual testing drops to zero, deployments go straight to production from CI, duplicate rule bugs vanish and developer morale rises under one code base to run them all.
AI-written summary · about
chapters (17)
- 0:00Introduction and context
- 3:41Problem with legacy monolith
- 7:12Goals and ambitions
- 8:16Technical refactoring approach
- 9:39Why Kotlin Multiplatform
- 10:00What is Kotlin Multiplatform
- 14:42KMP architecture layers
- 15:25Common vs platform-specific code
- 17:10KMP project setup
- 18:35Getting started with KMP
- 19:18Code structure example
- 21:46Publishing and consuming KMP
- 22:30Testing and deployment confidence
- 23:14Live documentation benefits
- 24:17Challenges and ongoing work
- 24:59Takeaways and results
- 27:07Closing and call to action
related talks
24mKotlin Multiplatform's Cross-Platform at Norway's 377-Year-Old Postal Service
47mKotlin Multiplatform's Cross-Platform Brilliance
26mKotlin Multiplatform in an MVVM World
34mKotlin Multiplatform: code sharing without compromise
41mKotlin Multiplatform In Production
32m10 myths about crossplatform mobile development with Kotlin
48mEffective Multiplatform Kotlin Development
36mExploring Kotlin Multiplatform