# React Native OTA updates that outlive CodePush (https://hotcodepush.com/react-native-code-push)

React Native code push on a maintained SDK after CodePush retired. A package swap keeps the workflow: signed, staged and reversible. Free for 1,000 MAU.

[CodePush retired 2025-03-31 · migrate](https://hotcodepush.com/docs/migrate/codepush)

Over-the-air (OTA) updates for React Native on a maintained SDK, a package swap from CodePush. Signed, staged and reversible. Free for 1,000 MAU.

[Get started](https://console.hotcodepush.com/register)

[Install with AI](https://hotcodepush.com/agents)

```
$ npx hotcodepush init
✓ sign-in — logged in as Anna
✓ organization — used organization Acme
✓ app — created app My App · React Native 0.82, New Architecture
✓ package — installed @hotcodepush/react-native-code-push
✓ configuration — wrote hotcodepush.json
✓ hook — wired the Xcode phase, the Gradle line and both hosts
✓ signing-key — generated; the private key stays in your file
▸ build — skipped, the packaging runs inside the upload
✓ release — created release #1 on production

$ npx hotcodepush release create
✓ created release #2 on production — devices update on next launch
```

init installs the package, edits both native hosts, wires the build step and publishes the first release. The next release create bundles per platform inside the upload and is your first OTA update.

## Built for today's React Native

A maintained SDK for current React Native, a patch instead of the whole bundle, and the one line that ships every merge from CI.

### A maintained SDK

One SDK built for current React Native, no legacy code paths to carry, no shims to maintain. Expo apps run the same module, wired in by its config plugin.

[Read the SDK reference](https://hotcodepush.com/docs/sdks/react-native)

### A patch, not the bundle

Your JavaScript bundle travels as a patch against the copy on the device when that is smaller than the file, otherwise as the full file, inside the same single download.

[How deltas work](https://hotcodepush.com/docs/concepts/update-delivery)

### Ship from CI

One CLI step after your build. Recipes for GitHub Actions, Bitrise, Codemagic, EAS Build and six more. The native build and its signing stay yours.

[How continuous delivery works](https://hotcodepush.com/continuous-delivery)

[Every safety feature, on every plan](https://hotcodepush.com/pricing)

## What you can update

Two layers in every app. An OTA update replaces one and the store ships the other.

Your JavaScript bundle and its assets ship over the air: a bug fix, a new screen, a changed text, a pure JavaScript dependency. The upload bundles them per platform, one release for iOS and one for Android. A native module, a new permission, a newer React Native runtime or native code of your own waits for the store. Each bundle carries the fingerprint of the native modules it was built against and reaches only the store builds that match.

[What is hot code push?](https://hotcodepush.com/docs/concepts/what-is-hot-code-push)

*The app as two layers: the JavaScript or web layer HotCodePush replaces at the next start, and the native layer only a store release changes*

## CodePush is gone. The workflow isn't

- A package swap, not a rewrite
- Deployment keys become channels
- Your release step stays one command

[Migrate from CodePush](https://hotcodepush.com/docs/migrate/codepush)

*Side by side: the CodePush release command and the HotCodePush one*

## What the SDK needs

The framework sets the minimum OS versions, never HotCodePush. Supported means proven by a release build in CI.

| Requirement | React Native |
| --- | --- |
| Framework versions | 0.82 and later, 0.82 to 0.87 proven |
| Minimum iOS | 15.1 |
| Minimum Android | 7.0 (API 24) |
| Architecture | New Architecture only: one Turbo Module, no legacy bridge |
| Package | @hotcodepush/react-native-code-push |

Last verified 2026-10-25.

[Supported versions and the deprecation policy](https://hotcodepush.com/docs/supported-versions)

From the team behind Capawesome

The same team, the same infrastructure and the same EU hosting that run live updates for Capawesome's customers today.

- **teams trust us**: 1,000+
- **SLA on two surfaces**: 99.9 %
- **from init to the first update**: < 60 s
- **data residency**: EU

Figures as of October 27, 2026.

## Coming from another tool

A package swap, not a rewrite.

### App Center CodePush

Retired 2025-03-31 with App Center. The workflow stays on an SDK we maintain: one release command, a channel per deployment, your signing key kept.

[Read the comparison](https://hotcodepush.com/alternatives/codepush)

### EAS Update

The React Native incumbent with Expo's own tooling. Here the fingerprint is the default, signing is free on every plan and rollouts pause themselves.

[Read the comparison](https://hotcodepush.com/alternatives/expo-eas-update)

### RevoPush

Keeps the CodePush client and its commands on a compatible server. HotCodePush ships and maintains an SDK of its own, built for today's React Native.

[Read the comparison](https://hotcodepush.com/alternatives/revopush)

### Stallion

The observability specialist; its rollback diagnostics lead the field. We add channels, version ranges and build matching, so no device is ever left out.

[Read the comparison](https://hotcodepush.com/alternatives/stallion)

## React Native questions

### Does Apple allow OTA updates for React Native apps?

Yes. Apple's developer agreement permits downloaded interpreted code, and Google Play exempts code that runs in an interpreter. A JavaScript bundle run by the app's own engine is exactly that. A native module, a new permission or a feature review never saw still goes through the store. [Store policies](https://hotcodepush.com/docs/store-policies)

### Which React Native versions are supported?

0.82 and later on the New Architecture, tested through 0.87. Minimum iOS 15.1 and Android 7 (API 24). Older versions are not supported. [Supported versions](https://hotcodepush.com/docs/supported-versions)

### Does it work with Expo?

Yes, through the Expo config plugin for SDK 55 to 58 in a development or release build. Expo Go cannot load native modules. [Expo OTA updates](https://hotcodepush.com/expo-ota-updates)

### How does the migration from CodePush work?

A package swap once the app runs on the New Architecture, which the SDK requires and CodePush never supported. Then create a channel for each deployment and ship a store release with the new SDK. From then on one release command replaces release-react, and the CodePush pipeline keeps serving the old builds until their users move. [Migrate from CodePush](https://hotcodepush.com/docs/migrate/codepush)

### How big is an update?

Only what changed, in one download. A device compares the new bundle's files with the ones it holds, the store build's included, and fetches the rest as one archive. The main JavaScript bundle inside it travels as a byte-level patch against the device's copy whenever the patch is smaller than the file. [Update size benchmarks](https://hotcodepush.com/benchmarks)

### How does it compare with RevoPush pricing?

RevoPush is cheaper at scale, and both are free for 1,000 devices. 10,000 cost $10 here and $9 on RevoPush's free plan with its per-thousand overage, 100,000 cost $100 here and $75 on Startup, and 1,000,000 cost $1,000 here and $500 on Professional, before egress there (verified 2026-11-05). [HotCodePush vs RevoPush](https://hotcodepush.com/alternatives/revopush)

## Your first OTA update in under a minute.

Free for 1,000 MAU. No credit card.

[Get started](https://console.hotcodepush.com/register) [Book a demo](https://cal.com/team/capawesome/hotcodepush-demo)

Questions? [Join our Discord](https://discord.gg/c5tTRAk2qW) or [contact us](https://hotcodepush.com/contact).
