LEVERAGE YOUR ANDROID KNOWLEDGE TO BOOST YOUR TEAM'S VELOCITY WITH REACT NATIVE
summary
Pinterest integrates React Native into existing Android and iOS apps by adding a third JS repo, symlinked for bundling, and packaging native RN libs as Maven artifacts. Engineering builds a React Native Event Bridge, shares the native image cache, and bridges API client, logging and experiments. An A/A experiment shows parity in performance with native screens. Integration adds ~2–3 MB per architecture and ~10k methods; four production React Native screens exist and over‑the‑air updates are under consideration.
AI-written summary · about
chapters (17)
- 0:00Introduction and background
- 3:33Why React Native at Pinterest
- 7:24Greenfield vs brownfield apps
- 10:55Technical integration overview
- 14:31APK size and method count impact
- 17:01Rendering React Native screens
- 18:26Type safety with Flow
- 19:54Native and JS bridge setup
- 21:03Bridging native APIs to JS
- 22:46Design system and UI components
- 24:32Navigation between native and RN
- 27:00Localization for React Native
- 29:06Bridging frameworks and logging
- 30:09Evaluation and A/A experiments
- 31:54Adoption and current usage
- 32:56Future technical improvements
- 33:59Q&A and closing remarks
related talks
35mBridging the Gap: How to use React Native in existing large native code bases
52mWhy you should use React Native for your next mobile app
50mWhy React Native Android Works
13mIntegrating React Native with Native Infrastructure
41mLessons Learned from React Native
39mReact Native - Unleash the power of React in your device
45mReact Native: Things we learned the Hard Way
45mAbout React Native inside your existing Android App
