Looking for a Microsoft CodePush alternative?
Microsoft retired the hosted CodePush service alongside App Center, so hosted CodePush users need to move. This is a migration, not just a comparison. Here is how Ubriot compares for React Native and Expo teams: native builds, OTA updates, release intelligence, and store submission on one flat plan.
- #412 iOSBuilding, Building
- #409 AndroidOn Google Play, Done
- #410 iOSNeeds you, Needs you
- #411 iOSSigning, Building
- #406 iOSOn TestFlight, Done
What Microsoft CodePush does well
Microsoft's React Native OTA update service, part of App Center and now retired, with the server open-sourced.
- Popularized over-the-air JS updates for React Native without an app-store round trip
- Simple deployment keys and rollback for shipping quick fixes
- Widely adopted, so a lot of RN apps still ship on it or its self-hosted successor
How Ubriot is different
Where Microsoft CodePush left off, here is how Ubriot approaches the same job for React Native teams.
1
A managed OTA system with named channels, runtime-version safety checks, and instant rollback, without running your own server
2
OTA lives alongside native builds, store submission, and push in one platform rather than a standalone update service
3
Before you publish, Ubriot warns if an update would target an older runtime than your users are on
4
The Ubriot CLI migrates an existing react-native-code-push setup by swapping the client and repointing the update URL, with dry-run by default
A fair caveat
CodePush proved out RN OTA and its server code lives on as an open-source community project; Ubriot is a managed alternative for teams who do not want to self-host that infrastructure.
Moving off Microsoft CodePush?
See how Ubriot's release pipeline fits your app.