Native, React Native, Flutter and More
summary
Compares native Android/iOS, React Native (JS) prototype and Flutter (Dart) prototype by actually building the same Unsplash photo list app in each stack and measuring load time, memory and CPU. React Native is fast to start but risks untyped JS, many libraries, Android bridging pain and obscure errors; Flutter gives type safety and a fast layout but is young and has smaller talent and native-bridge work; native delivers best out-of-box performance and OS feature access but costs more and duplicates work. Proposes writing goals, prototyping, measuring and scoring results.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:22React Native overview
- 7:52Flutter overview
- 8:55Native development pros and cons
- 10:19Decision making process
- 13:09Prototyping and measuring
- 16:40Separating fact from opinion
- 19:26Summary and resources
related talks
31mThe performance myths of React Native
29mWhich one is for me: React Native/Flutter/Native
01h 01mFlutter vs React: A Native Developer's View
36mWhat I learnt by building the exact same app in Kotlin (Native Android), Nativescript and Flutter
24mThe Performance Myths of React Native apps
11mMobile development in 2019: native versus cross-platform
40mChoosing The Best Mobile Framework
27mBuilding high quality mobile apps with React Native