Cross-platform tools in the real world
summary
Compares Flutter, Kotlin Multiplatform and native stacks and reports what actually breaks in production: Flutter bundles its engine which avoids host runtime issues but increases app size; Kotlin Multiplatform for Android‑first business logic lets teams share models and rules without forcing iOS devs to change. Notes real failures at scale (Airbnb, Dropbox) from integration, performance and staffing, highlights WebAssembly as future option, and stresses answering deployment, maintenance and team‑size questions before choosing.
AI-written summary · about
chapters (8)
- 0:00Introduction to cross-platform
- 2:02History of cross-platform UI
- 7:02Why cross-platform failed so far
- 14:58Why cross-platform still matters
- 23:10Modern cross-platform solutions
- 33:15Flutter and WebAssembly potential
- 36:51Future of native vs cross-platform
- 38:17Q&A and closing
related talks
56mBattle Royale of Cross-Platform Frameworks
01h 00mMobile App Architecture: How to Conquer the Giant!
48mEffective Multiplatform Kotlin Development
13mUsing multiplatform frameworks to target Android in emerging markets.
26mKotlin Multiplatform in an MVVM World
30mCross-platform Collaboration Patterns
39mCross-platform UI Engines Rendering Performance
33mMultiplatform Functional Architecture