Working Across Platforms
summary
Compares concrete cross‑platform choices: React Native bridge uses JS derivatives and an async FIFO message queue that often becomes a serialization bottleneck; Flutter → Skia fully reimplements UI in Dart, outputs a layer tree to the GPU for smooth frames and uses separate task runners; Kotlin Multiplatform expect/actual shares logic, outputs Kotlin Native binaries and interoperates via Objective‑C/C bindings for iOS. Advises pick UI‑vs‑logic sharing and wrap‑vs‑reimplement based on where serialization, threading, and native API mapping create risk.
AI-written summary · about
chapters (7)
- 0:00Introduction to cross platform
- 4:59Logic vs UI sharing
- 7:48Reimplement vs wrap UIs
- 11:39React Native architecture
- 20:00Flutter architecture
- 28:01Kotlin Multiplatform overview
- 38:13Summary and takeaways
related talks
21mBridging, Compiling, and Rendering: How Cross-Platform Frameworks Work
11mMobile development in 2019: native versus cross-platform
41mCross-Platform Fireside Chat
18mCross-Platform Development as a Native Mobile Developer
39mCross Platform & Beyond
23mThe State of One Codebase For All The Platforms
40mChoosing The Best Mobile Framework
21mNative, React Native, Flutter and More