Over-the-air updates · React Native · Electron · Tauri
Stop making yourusers wait.
Ship fixes to React Native, Electron and Tauri apps over the air. Skip the store review queue for JS and UI changes. Users get the update on next launch.
One fix, two paths
illustrativeStore release vs. OTA
The fix is done. Why are your users still waiting?
Store release
- Build a new binary
- Submit and wait for review
- Stage the rollout
- Wait for users to update
time to fix = store queue + update rateDaysZephyr OTA
- Publish the new bundle
- Point production at it
- Users get it on next launch
time to fix = one releaseNext launchNative code changes still go through the store. JS, UI and web-layer changes ship over the air.
Why teams use it
Release on your schedule, not the store's.
Fix it today
A production bug does not wait for a review queue. Publish the fix and users get it on next launch.
Roll back on the device
Every version stays available. Point the app at the last good one and users have it on next launch.
Choose who gets it
Send a version to an internal environment first, then to everyone. Same build, no rebuild.
How it works
Three steps. No new pipeline.
Add the Zephyr plugin to the bundler you already use for your React Native, Electron or Tauri app.
Each build uploads as an immutable version. Nothing goes live until you say so.
Point an environment at the version. Apps load it on next launch.
Book a demo
See an OTA updateland on a real device.
30 minutes with an engineer. We push an update to a React Native, Electron or Tauri app on the call.
- OTA for React Native, Electron and Tauri
- Rollback without a store release
- How it fits your release process