Using multiplatform frameworks to target Android in emerging markets.
summary
Compares native, hybrid and compiled-native approaches with concrete tradeoffs: Ionic is a webview wrapper with poor performance on low-end hardware; React Native and NativeScript render UI natively but keep a JavaScript bridge and can become hard to maintain as features grow (Airbnb reports ~60% shared code); Flutter compiles to ARM libraries for better speed but lacks many platform components so it fits prototypes or MVPs. Notes real problems in emerging markets: low‑end devices and unreliable push notifications.
AI-written summary · about
chapters (9)
- 0:00Introduction to multiplatform
- 1:53Native vs hybrid vs compiled
- 4:24Write once deploy everywhere
- 6:10Popularity and community support
- 7:35Performance considerations
- 8:18Real-world scenarios
- 9:43Speaker introduction and experience
- 10:25Emerging markets challenges
- 11:50Choosing the right framework
related talks
21mIs Native iOS Dev Always Best?
46mCross-Platform Mobile Development vs. Native
39mCross-platform tools in the real world
56mBattle Royale of Cross-Platform Frameworks
23mThe State of One Codebase For All The Platforms
39mCross-platform UI Engines Rendering Performance
42mBlurring the Line between Native and Web
31mBridging The Gap Between Mobile Platforms