PushOTA Open console

REACT NATIVE UPDATES, UNDER YOUR CONTROL

Your next fix.
Already on its way.

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.

PushOTARELEASE WORKFLOW

EXAMPLE APP / IOS

A small fix.
A better experience.

Updated checkout experience

01
Test in StagingApproved test devices
✓
02
Promote to ProductionThe same signed package
✓
Built for a careful release.
One release workflow.iOS + AndroidSigned updatesStaging → ProductionRollback protection

A LITTLE HELP GETTING STARTED

Set up with Codex
or Claude.

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 guide

Start in your app’s project.

  1. Open your app’s project in Codex or Claude Code.
  2. Copy the instruction below and paste it into your agent.
  3. Review the changes and complete native build and device testing.

View setup instruction

Uses 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

A release process
you can come back to.

Keep your project connected. Publish from the terminal. Manage what ships from one console.

01 / CONNECT

Set up once.

A guided setup connects your project, prepares its signing key and helps you configure the native app.

See the setup guide
02 / VALIDATE

Try it with your team.

Pair test installations to receive Staging updates, including on the same native version your customers use.

Learn about test devices
03 / RELEASE

Ship with control.

Promote your signed package, adjust its rollout, monitor reported results and publish a rollback from the dashboard.

Explore release controls
FROM YOUR CONNECTED PROJECTnode ota.cjs publish ios --deployment Staging
Publishing guide

CONFIDENCE IS PART OF THE WORKFLOW

Move quickly.
Keep a way back.

Your update is one part of a running app. Release controls should respect everything around it.

Read about release safety

Verify before applying.

Package signatures and native compatibility checks help keep the right update on the right app.

Keep the healthy version.

Readiness checks and rollback protection help recover from an update that fails to start.

Give each team its space.

Organisations, app permissions and scoped publishing credentials separate access across projects.

A FEW THINGS TO KNOW

Clear expectations.
Better releases.

What can I update with PushOTA?

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.

Do Staging and Production need different store builds?

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.

What if an update cannot download?

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?

Start with a connected app.

Open the setup guide