Expo + Bundle Drop

Expo OTA Updates with Bundle Drop

Bring Bundle Drop's hybrid delivery, targeted rollouts, and automatic recovery to Expo—without leaving the Expo development workflow.

Expo SDK 54–57Managed and CNGEAS BuildiOS and AndroidOld and New Architecture

Unlimited MAU on every plan. No per-user fees.

Native when it matters

Stay inside the Expo workflow you already use

Bundle Drop follows Expo's configuration and build model. Keep native folders absent in managed/CNG projects, or let a reviewed layered prebuild update projects that commit them.

Keep Expo development intact

Expo Go, Metro, and development clients behave normally while Bundle Drop stays out of the debug path.

Generate native integration safely

The Expo config plugin applies through prebuild, expo run, or EAS without asking you to hand-edit generated entrypoints.

Publish from one CLI

Upload compatible JavaScript and assets to a channel with option-free Expo platform commands.

Your Expo project

One workflow, two modes

SDK 54–57

Development

Expo Go or dev client

Use the development loop you already know.

Metro stays in control

Bundle Drop OTA remains disabled while debugging.

Release

Expo app config

Keep native configuration in the Expo project.

Bundle Drop plugin

Prebuild, expo run, and EAS apply the integration.

Release binary

The installed app owns a compatible runtime line.

OTA channel

Ship compatible JavaScript and bundled assets.

Release control for Expo

Faster delivery without giving up safety

Bundle Drop brings the complete OTA release workflow to Expo, from efficient delivery to audience control and recovery.

Hybrid delivery

Devices receive a compact binary patch when it is efficient, with a complete verified bundle ready as the reliable fallback.

Small patch

When efficient

Full bundle

Always available

Targeted rollouts

Release by channel, percentage, or user properties so the right Expo installs receive the right update at the right time.

matched audience

Automatic recovery

Native startup protection returns an unhealthy update to the previous proven-healthy OTA or the embedded bundle.

Native bundleLast healthy OTA
Failed startup returns to safety

Still choosing between Expo-native, managed, and self-hosted OTA? Compare React Native OTA tools for Expo and bare apps.

Three commands to a verified setup

Install through Expo. Let Bundle Drop do the rest.

Login detects the project, registers the config plugin, preserves Expo Metro behavior, and previews every setup change before it is applied. Doctor verifies the result.

Follow the complete Expo setup
expo-app — bash

Compatibility on your terms

One runtime model, two levels of control

Use simple literal runtime versions by default, or opt into exact Expo build fingerprint enforcement when your release process requires it.

Recommended default

Own the runtime version

Use the same literal runtime model across Expo and bare React Native. Your team decides when a native compatibility line changes.

  • Keep the runtime for compatible JavaScript and asset updates
  • Bump the affected platform and rebuild after native changes
  • Upload without Expo build receipts

Optional strict mode

Bind updates to an Expo build

Let the evaluated Expo runtime policy and native fingerprint become the upload authority when exact build proof is part of your release process.

  • Match the exact local or EAS build receipt
  • Reject uploads from changed native inputs
  • Use clean-worktree enforcement for layered native builds

Start shipping OTA updates in minutes

Bundle Drop gives you everything you need to deploy React Native updates instantly. Join developers shipping with confidence.

Get started free