The Death of "Write ONce, Run Everywhere"
summary
Argues that “Write Once, Run Everywhere” fails in practice because PhoneGap/Cordova/Trigger.io force webviews with single-threaded rendering, memory limits, plugin gaps and visible UI mismatches; hybrid apps work well as prototyping but not for polished UX. Presents concrete alternatives: React Native (native controls, no web views no CSS no HTML but alpha and Android support lagging), NativeScript and Titanium, compares code-sharing tradeoffs and engineering pain points so teams can decide whether to accept two native codebases or keep hybrid speed.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:11A Eulogy
- 2:05Goals of writing Hybrid applications
- 2:18Build: Run it cross- platform
- 4:31UX Gap
- 5:55Design Issues
- 7:43Code issues
- 8:20The Core
- 9:14SINGLE THREAD
- 9:30Memory management
- 11:46Facebook introduces react-native
- 16:51A JavaScript V8 engine sounds familiar...
- 17:56Gotchas
- 19:04The future
related talks
48mMobile Apps with JavaScript - There's More Than Web
37mEffective mobile applications prototyping with JavaScript
41mBuilding a cross-platform native app with JavaScript
31mEnding the Web Versus Native Debate
59mOne Codebase to Rule Them All - Using React Native Everywhere
04mJonathan Stark interviewed at OSCON 2010
51mWrite once, run everywhere: ambitious cross-device web apps
27mBuilding high quality mobile apps with React Native
