Lessons Learned from React Native
summary
Airbnb adopts React Native in 2016, ships 220 unique screens backed by 80,000 lines of JavaScript plus 40,000 lines of JS infrastructure, but React Native remains ~15% of mobile work and needs at least two full‑time engineers for upgrades, bridging native APIs, and fix‑it crises; crossplatform adds a third platform, complicates state sharing, testing, and hiring. Airbnb then builds and open sources Mavericks, an Android Kotlin architecture that pilots with 14 engineers, produces 50 screens, and scores 13/14 ratings ≥8.
AI-written summary · about
chapters (8)
- 0:00Introduction and talk scope
- 1:10History of React Native at Airbnb
- 8:56Organizational challenges with crossplatform
- 14:09Support and maintenance hurdles
- 21:13Native vs React Native decision process
- 26:49Lessons learned and sunset decision
- 28:15Introducing Mavericks framework
- 39:46Q&A and closing remarks
related talks
42mLessons Learned from React Native at Airbnb
45mSunsetting React Native at Airbnb
28mShould I use React Native too?
07mKeynote Part 1
51mRapid App Development With React Native: Lessons Learned at NSB
45mReact Native: Things we learned the Hard Way
29mA practical approach to building truly native cross-platform applications at scale
28mReact Native in the "Brown Field"