Over-the-air updates: why your app can be fixed today instead of next week
How a fix reaches your customers' phones without waiting for an App Store review, what it can and cannot change, and why it matters when you pick a developer.
When something breaks in an app, the owner usually hears one of two things: it will be in the next release, or Apple has to approve it first. Both mean days. There is a third answer, and it is the one you want.
Two kinds of change
An app is a shell that the store approved and a bundle of code that runs inside it. A native change, like a new permission or a new camera feature, changes the shell and needs a store review. A code change, like a wrong price, a broken button or a new screen built from existing parts, only changes the bundle.
What over-the-air means
The bundle can be replaced without touching the shell. The app checks for a new bundle when it opens, downloads it, and runs it next time. No store review, no waiting for the customer to update. We ship these to production apps in both stores as a normal part of support.
- 01Fixes and copy changes: same day.
- 02New screens built from existing components: same day.
- 03New native capabilities: a store release, usually a few days.
Ask how a bug fix reaches users and how long it takes. If every change means a store release, support is measured in weeks.
The catch, and how we handle it
An over-the-air bundle has to match the shell it runs in. Ship a bundle that expects a native module the shell does not have and the app crashes on open, then rolls itself back. So every app we run has a runtime version pinned across the native files, and a preflight check runs before every update. That discipline is the difference between a tool that saves you days and one that takes your app down.
What to ask a developer
Ask how a bug fix reaches users and how long it takes. If the answer involves a store release for every change, your support costs will be measured in weeks.
Want this built for your business?
One call. A written scope, fixed price and ship date the next day. A working version in your hands by the end of week one.
Online pickup ordering for a bakery, butcher or candy shop: what you actually need
What online ordering should do for a shop that sells over a counter, what it should not do, and how to tell if your shop is ready for it.
Getting an app approved: the checklist we run before every submission
The rejections we have actually received from Apple and Google, turned into a checklist that runs before any build goes up.