A quick look at how Expo's EAS Update lets you push JavaScript and assets over‑the‑air, cutting release friction while keeping users on the latest code.

expo-eas-update-ota-tips.md

Insight

Expo's EAS Update turns the traditional app‑store release cycle on its head. Instead of bundling every change into a new binary, you can ship JavaScript, images, and fonts directly to devices that already have the native shell installed. This works best for bug fixes, UI tweaks, or feature flags that don’t require native module changes. Because the update is fetched at runtime, you retain the ability to roll back instantly by publishing a previous manifest.

Example

// eas.json – enable OTA for the "production" channel
{
  "cli": { "version": ">= 3.0.0" },
  "build": { "production": { "distribution": "store" } },
  "submit": { "production": {} },
  "update": {
    "fallbackToCacheTimeout": 0,
    "url": "https://u.expo.dev/<project-id>"
  }
}

Takeaway

Treat EAS Update as a fast‑lane for pure JavaScript changes: push small, non‑native updates instantly, but keep a clear versioning strategy and fallback to the store for any native code modifications.