Comparison
AirBuild vs EAS Update
EAS Update is Expo's OTA service for React Native; AirBuild serves the same open Expo Updates v1 protocol — so `expo-updates` clients work against AirBuild — while also covering Flutter patches, crash-rate auto-pause, and full IPA/APK distribution with UDID capture in the same platform.
| Feature | AirBuild | EAS Update (Expo) |
|---|---|---|
| React Native OTA updates | Yes | Yes |
| Client protocol | Open Expo Updates v1 | Expo Updates |
| Requires an Expo/EAS account | No | Yes |
| Flutter OTA patches | Shorebird protocol | No |
| Staged rollout percentages | Yes | Yes |
| Automatic pause on crash threshold | Yes | Client-side fallback only |
| Rollback | One command, server-side | Re-publish previous update |
| Binary distribution (IPA/APK links + QR) | Yes | No |
| Automatic UDID capture for ad-hoc iOS | Yes | No |
| Webhooks + REST API + Go CLI | Yes | EAS CLI + GraphQL API |
Which should you pick?
EAS Update is the default choice inside the Expo ecosystem and works well there. AirBuild fits teams that want the same `expo-updates` wire protocol on their own terms — plus Flutter patches in the same system, automatic server-side rollout pausing when crash rates spike, and binary distribution to testers from the dashboard where updates already live.
Frequently asked questions
Does AirBuild work with the `expo-updates` library?
Yes — AirBuild implements the open Expo Updates v1 protocol, so apps built with `expo-updates` fetch manifests and bundles from AirBuild's servers by configuring the update URL.
Do I need an Expo account to use AirBuild's React Native OTA?
No — `airbuild codepush react-native publish` builds your bundle with `npx expo export` locally and serves it from AirBuild; no EAS account or plan required.
Can AirBuild pause a rollout automatically?
Yes — AirBuild tracks install failures per update and auto-pauses a rollout when the failure rate crosses the configured threshold, then notifies you by webhook and audit log.