Skip to content
Help center

Update your app without the stores (OTA updates)

Send code, text and image changes straight to the apps already installed with EAS Update, and know which changes still need a new build and review.

Updated 3 min read
On this page
  1. What an update can change
  2. What needs a new build
  3. Send an update
  4. When users get it
  5. Updates and store rules
  6. FAQ
  7. Related

Once your app is installed on phones, every new version normally goes through a build and the stores' review. For most changes there is a faster way: an over-the-air update (OTA). You send the new code from FromScratch, and the apps already installed download it on their own, without a new store version. This is done with Expo's service EAS Update, from Dashboard › Mobile.

What an update can change

An update replaces the part of your app the agent writes day to day:

  • the screens, their layout and their texts;
  • the app's logic: buttons, forms, calculations, calls to your services;
  • the images and other files that are part of the project.

What needs a new build

Some changes touch the native part of the app, which an update can't replace. They need a new build and, for the stores, a new version:

  • a new module with native code (camera, notifications, maps… added by the agent);
  • a new permission or the text that explains it;
  • the icon, the splash screen, the app's name or identifiers;
  • a new Expo version.

If you're unsure, ask the agent: it knows which of its changes are native. A safe habit is to make a new build when you add a new phone feature, and use updates for everything else.

Send an update

  1. Ask the agent for your changes and check them in the preview and on your phone.
  2. Open Dashboard › Mobile, card OTA updates (EAS Update).
  3. Write an Update message that says what changed, for example « New menu and cart fix ». It's for you: users don't see it.
  4. Click Publish. FromScratch sends the update to Expo (« Publishing the update »). The update then appears under Latest updates.
The OTA updates card with its message field and the list of updates
Write a message, Publish, and the update shows up under Latest updates.

Nothing is sent automatically: the agent's changes only reach installed apps when you click Publish.

Warning

the very first publish turns updates on in the project. Only builds made after that first publish can receive updates. So: publish a first update, make a new build, send that build to the stores, and your later updates will reach it.

When users get it

An installed app checks for an update when it is opened. It downloads it in the background and usually shows it the next time it is opened. Users don't need to do anything, and they don't see a store update.

Updates and store rules

Google and Apple accept updates that fix and improve your app. They don't accept updates that turn it into a different app or skip their review for a major new feature. For a big change, send a new version through the stores: see Publish your app on Google Play and Publish your app on the App Store.

FAQ

Can I undo an update?

Ask the agent to go back to the previous state (or use Versions), then publish again: the new update replaces the faulty one. See Versions: undo anything.

Do updates count toward my Expo quota?

EAS Update has its own allowance in Expo's plans, separate from builds. Check your usage on expo.dev; FromScratch charges no credits for publishing.

Was this page helpful?