Over-the-Air Update OTA

An over-the-air update is a change that reaches everyone using your app without anyone downloading a new version from the store. The app on the phone stays the same. What changes is the material it pulls from your server the next time someone opens it.

More can be moved this way than most owners expect. Prices, opening hours, delivery fees, the text on a screen, the photos on the home page, which branches show in the list, the tax rate, the wording of a warning. All of that can live on your server instead of inside the app file. A restaurant can take a dish off the menu at nine in the morning, and every phone shows the shorter menu by ten.

Some changes still need a store release, and no supplier can argue their way around it. A new screen. A new way to pay. The first time the app asks for the camera, the location or permission to send alerts. Apple and Google review those themselves, and the wait runs from a few hours to a few days. Plan for it.

The line between the two is a decision made early, not later. If a price sits inside the app file, changing it costs you a release and a wait. If it sits on the server, it costs one click. When Linkysoft starts a mobile app project, we ask the owner which parts they expect to change every month, and we move those to the server before the first screen is drawn.

There is a cost people rarely hear about first. Anything kept on the server needs a place where a human can edit it, so the app quietly arrives with a small control panel behind it, usually the same web application the business already works in. Leaving that panel out is the common mistake. It saves a little money at the start, then costs a phone call to the developer every time a price moves.

So ask one question before you sign anything. Show me the screen where I change a price myself. If the honest answer is that they will do it for you, you have bought a release cycle rather than an app. Linkysoft counts that screen as part of the work, not an extra.