The Journey of React-Native @ Flipkart
Article Summary
Talha Naqvi from Flipkart reveals how React Native cut their A/B testing cycles in half while serving 100M+ users. The secret? Strategic compromises and custom infrastructure.
Flipkart, India's largest e-commerce platform with 400M weekly visits, adopted React Native in 2016 to solve a critical problem: building features three times (web, Android, iOS) was killing productivity. This deep dive shares their 4-year journey, including what worked, what didn't, and the custom tools they built.
Key Takeaways
- A/B testing cycles dropped from 6 weeks to 3 weeks using OTA updates
- Built custom bundle diffing to reduce payload sizes by over 90%
- Created recyclerlistview after native backed solutions failed cross platform sharing
- Kept homepage fully native because React Native was 300-500ms slower on launch
- Achieved 95% code sharing between iOS and Android on their Grocery experience
Flipkart successfully scaled React Native across their entire mobile stack by setting clear performance targets, building custom infrastructure for OTA updates, and strategically keeping performance-critical screens native.
About This Article
Flipkart's React Native Android apps were loading pages slower than native versions. On Snapdragon 625 processors, launch times fell behind by 300-500ms.
Flipkart stopped rebuilding React Instance Managers every time users switched between sections. Instead, they reused the same managers and started running React instances in the background before users actually navigated to React Native pages. This cut down on JS parsing overhead.
The performance improvements let Flipkart meet their targets and use React Native on more pages. They kept the homepage fully native because of launch time limits, but expanded React Native to other areas of the app.