Expo EAS · From code to your users

Expo EAS · From code to your users A workflow diagram generated by Archify. 01 / Develop & decide 02 / New native binary 03 / Compatible update Develop · App code + assets · Develop & decide · CLI: npx expo start --dev-client Develop App code + assets Test locally · Development build · Develop & decide · CLI: eas build --profile development --platform all Test locally Development build Check runtime · Native compatibility · Develop & decide · CLI: npx expo config --type public Check runtime Native compatibility EAS Build · Signed iOS / Android app · New native binary · CLI: eas build --profile production --platform all EAS Build Signed iOS / Android app EAS Submit · Upload to app stores · New native binary · CLI: eas submit --platform all EAS Submit Upload to app stores Store release · Review → release → install · New native binary Store release Review → release → install Preview update · JavaScript + assets · Compatible update · CLI: eas update --channel preview --environment preview Preview update JavaScript + assets Verify on device · Matching preview runtime · Compatible update Verify on device Matching preview runtime EAS Update · Production channel · Compatible update · CLI: eas update --channel production --environment production EAS Update Production channel Installed app · Download → next launch · Compatible update Installed app Download → next launch new binary needed compatible JS / assets matching runtime tests pass verified Legend User UI Agent logic Policy Cloud service External system

Build ≠ Submit ≠ Release

  • • Build creates the binary; Submit uploads it.
  • • Complete store review and release to reach users.

Updates need compatibility

  • • Target channel, platform, and native runtime must match.
  • • Native dependencies or SDK changes require a new build.

Automate with EAS Workflows

  • • Hover or focus a step to see its relevant CLI command.
  • • Steps without commands happen on a device or in a store console.