Choosing The Best Mobile Framework
summary
Compares first‑party native (Swift/ObjC, Java/Kotlin), PWAs, and cross‑platform native stacks (Xamarin/Microsoft, React Native/Facebook, Flutter/Google), gives concrete tradeoffs: 10 ms native tap latency versus PWA ≈100 ms and original web ~300 ms, claims 95–98% of apps won’t suffer performance issues, warns PWAs lack AR, geofencing, vibration, highlights hiring and maintenance costs, reports a shipped Xamarin app sharing ~95% code between iOS and Android, and notes Flutter’s bespoke UI and Xamarin’s full native API access.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:47Choosing a mobile framework
- 3:53Framework selection key points
- 11:12First-party native apps
- 22:13Progressive web apps
- 36:44Advantages of progressive web apps
- 41:35Cross-platform native apps
- 42:39Xamarin deep dive
- 49:23React Native vs Flutter
- 57:10Framework recommendations
- 59:20Conclusion
related talks
40mChoosing The Best Mobile Framework
11mMobile development in 2019: native versus cross-platform
46mCross-Platform Mobile Development vs. Native
21mNative, React Native, Flutter and More
37mThe Mobile Web Second Edition" First-Class Citizen on Your Device Now"
56mPWA vs NATIVESCRIPT
39mWorking Across Platforms
01h 02mSmaller not taller: defeating the mobile app architecture giant