Over-the-Air App Updates
Update your app instantly. No store review. No binary rebuild. Push JavaScript changes to all users in seconds.
What Are OTA Updates?
Mobile apps have two layers: the native binary (compiled iOS/Android code) and the JavaScript bundle (your app logic and UI). Over-the-air updates let you replace the JavaScript bundle without rebuilding or resubmitting the native binary.
This means you can fix bugs, update content, tweak UI, and add features — all pushed instantly to users without waiting for Apple or Google review. Users get the update the next time they open the app.
Release Channels
Mobiforge supports three release channels for controlled rollout:
Preview
Test updates on your own device before anyone else sees them.
Staging
Share with beta testers or team members for feedback before going live.
Production
Push to all users. Updates appear the next time users open the app.
Instant Rollback
If an update causes issues, roll back to the previous version instantly. No new build, no store submission, no waiting. One click and all users get the previous stable version on their next app launch.
How It Works Under the Hood
Mobiforge implements a custom Expo Updates protocol:
- When you push an OTA update, Mobiforge bundles your JavaScript code and assets
- The bundle is uploaded to CDN-backed storage (Backblaze B2)
- When users open your app, it checks the manifest endpoint for updates
- If a new version is available, the app downloads and applies it
- The update takes effect on the next app launch
When to Use OTA vs Full Rebuild
| Change Type | Method |
|---|---|
| UI tweaks, styling changes | OTA Update |
| Bug fixes in app logic | OTA Update |
| Content or copy changes | OTA Update |
| New screens or navigation | OTA Update |
| New native permissions | Full Rebuild + Store Submission |
| New native modules | Full Rebuild + Store Submission |
| SDK version upgrade | Full Rebuild + Store Submission |
Available on Growth and Studio Plans
OTA updates are available on the Growth plan ($99/mo) and above. Combined with automated store publishing, you have a complete mobile CI/CD pipeline.