The past, present, and future of React Native
summary
Expensify migrates from a 2010 closed-source mobile framework to React Native and react native web, replacing a legacy V8 engine by porting to JavaScriptCore and rewriting the Android bridge to meet Android 64-bit deadlines. New Expensify is fully open source, reuses nearly 100% of code across platforms, and grows an external contributor network of ~1,100 freelancers that fixes ~2,000 bugs and earns 1.2 million dollars in payouts in 2022. Plans include a one-day “switcheroo” user migration, ~20 PRs for Fabric/TurboModule support, and full new-architecture adoption by year-end.
AI-written summary · about
chapters (13)
- 0:00React Native at Expensify
- 2:34Big swings with Super Bowl ads
- 4:01Old framework challenges
- 7:56Costly internal framework
- 9:00Rewrite with React Native
- 10:24Web and mobile sync
- 11:29Open source acceleration
- 13:56Community code improvements
- 14:57Growing contributor community
- 16:06Migrating users to new Expensify
- 17:10New React Native architecture
- 17:50Sponsoring open source dependencies
- 18:34Expensify’s React Native vision
related talks
17mDispatches from React Native
01h 13mMigrating to React Native: A long-term retrospective
25mReasons to give React Native a(nother) try
07mFrom Native to React Native
50mReact Native hindsight from Pl@ntNet
28mShould I use React Native too?
11mTrailing React Native in a Legacy Mobile App
35mMigration Web (Angular) to Mobile Development (React Native)