Delivery for React Natives
Delivery in React Native is the process of turning a working app into signed builds, publishing them to Google Play and the Apple App Store, and updating them afterwards. It covers app identifiers, signing keys, store listings, EAS Build and Submit, over-the-air updates for JavaScript changes, and environment-specific configuration.
Stage: Quality and Release · Part of the React Native roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Produce a signed Android release bundle and an iOS archive
- Configure separate development, staging and production environments
- Submit a build to TestFlight or Google Play internal testing
- Ship a JavaScript-only fix with EAS Update where store rules allow
- Plan versioning with version name and build number
Delivery interview questions
What can an over-the-air update change and what can it not?
An OTA update can replace the JavaScript bundle and assets. It cannot change native code, add a new native library or alter permissions, because those live in the installed binary. Any change to native parts needs a new store build, and stores restrict what updates may alter.
What is the difference between versionCode and version name on Android?
The version name is the label users see, such as 1.2.0. The versionCode is an integer the Play Store uses to order releases, and it must increase with every upload. iOS has a similar pair: the marketing version and the build number.
Where Delivery fits in the React Native roadmap
Delivery belongs to the Quality and Release stage (advanced level). Ship.
Other units in this stage
Back to the full React Native roadmap