Set up once.
A guided setup connects your project, prepares its signing key and helps you configure the native app.
See the setup guideREACT NATIVE UPDATES, UNDER YOUR CONTROL
Deliver JavaScript and asset updates to your iOS and Android apps. Test with your team, release with confidence, and recover when something goes wrong.
Works with bare React Native. No Expo integration required.
EXAMPLE APP / IOS
Updated checkout experience
A LITTLE HELP GETTING STARTED
Let Codex or Claude Code handle the integration in your React Native project. Your agent inspects the app, asks about missing details and runs the checks.
Read the AI setup guideUses your existing agent. A PushOTA account and access to the app are required. Your agent will ask when it needs your input.
FROM YOUR PROJECT TO YOUR USERS
Keep your project connected. Publish from the terminal. Manage what ships from one console.
A guided setup connects your project, prepares its signing key and helps you configure the native app.
See the setup guidePair test installations to receive Staging updates, including on the same native version your customers use.
Learn about test devicesPromote your signed package, adjust its rollout, monitor reported results and publish a rollback from the dashboard.
Explore release controlsnode ota.cjs publish ios --deployment StagingCONFIDENCE IS PART OF THE WORKFLOW
Your update is one part of a running app. Release controls should respect everything around it.
Read about release safetyPackage signatures and native compatibility checks help keep the right update on the right app.
Readiness checks and rollback protection help recover from an update that fails to start.
Organisations, app permissions and scoped publishing credentials separate access across projects.
A FEW THINGS TO KNOW
Compatible JavaScript and bundled assets in a React Native app that already includes the OTA SDK. Changes to native dependencies, native configuration or the signing trust key require a new native store build. Read the compatibility guide.
You can use one Production-configured native build. Approved paired test installations receive Staging; regular installations receive Production. Your app chooses where to expose the reusable pairing panel. See the routing workflow.
The app keeps its last healthy version usable and can retry later. Required updates follow the same recovery principle. Learn about readiness and rollback.
READY FOR YOUR NEXT RELEASE?