A clear breakdown of what React Native changes can be deployed over the air versus what still requires a full App Store or Google Play submission. Covers the two-layer architecture (native shell vs. JavaScript bundle), lists eligible changes (JS logic, UI components, styles, assets, config, copy), and lists ineligible ones (native modules, permissions, native SDKs, ios/android directory changes). Also addresses grey areas like new screens, push notification handling, and in-app purchases, explains Apple and Google's OTA policies, and provides a five-question decision framework for evaluating any specific change.
Table of contents
How React Native apps are structured and why it mattersWhat you can deploy over the airWhat still requires a store releaseThe grey areas and how to think about themApp Store and Google Play policy: what you need to knowA practical decision frameworkFrequently Asked QuestionsWhat React Native changes still require an App Store or Google Play submission?Can I add a new screen to a React Native app using OTA updates?Do Apple and Google allow OTA updates for React Native apps?Can I update push notification handling with an OTA update?Related readingSort: