What's Next for Cross Platform Mobile Development?

on YouTube ↗41m

" summary

Describes using server-driven UI delivered as JSON to cut native release friction and accelerate experiments by replacing multi-week client rollouts with server-side changes. Implements a transport object and renders UI on-device using Yoga/flexbox with native view mounts (mentions Litho, ComponentKit, JavaScript bundles and JavaScriptCore); reports typical 2+ week native release cycles and heavy version fragmentation in some regions (40–42% old versions) while noting added latency, offline and animation issues and legal constraints.

AI-written summary · about

" chapters (15)

1. 0:00Introduction
2. 3:43Server-driven UI
3. 9:06Mobile feature challenges
4. 15:07Existing solutions limits
5. 19:30Server-driven rendering
6. 22:18Client-side Yoga Litho
7. 26:20Server-driven UI benefits
8. 28:35Disadvantages constraints
9. 30:21Legal considerations
10. 31:07Innovation vs goals
11. 32:10Q&A Backend integration
12. 33:54Q&A Performance cost
13. 36:42Q&A Declarative UI CMS
14. 37:45Q&A Serialization Yoga
15. 39:32Q&A Closing

" related talks

• 39mWorking Across PlatformsChristina Lee · droidcon NYC 2019
• 11mMobile development in 2019: native versus cross-platformMiriam Busch · The Lead Developer London 2019
• 48mMobile Apps with JavaScript - There's More Than WebHeiko Behrens · Mobilism 2012
• 46mCross-Platform Mobile Development vs. NativeJaime Fernández · Commit Conf 2019
• 47mCross Platform Mobile FishbowlMike James, Niels Sthen Hansen · GOTO Copenhagen 2015
• 27mBuilding high quality mobile apps with React NativeParashuram Narasimhan · State of platforms: Fragments Ahmedabad 2019
• 21mBuilding Cross-Platform Component Libraries for Web and Native with ReactPerttu Lähteenlahtii · React Advanced 2021
• 30mReact Native's New ArchitectureParashuram N · React Conf 2018