Ship to the App Store and Play Store

Prerequisites: a working Expo app (any project from this roadmap), an Apple Developer account ($99/year) for iOS, a Google Play Developer account ($25 one-time) for Android, a free Expo account.

Version note: verified against current Expo documentation as of July 2026: EAS Build and EAS Submit remain the current, actively maintained path from source to store, and EAS Build can produce signed iOS binaries from Windows/Linux/macOS since builds run in the cloud — a local Mac is only required for local builds, not EAS-hosted ones. First submissions to both stores still require at least one manual upload/app-creation step (Apple: create the app listing in App Store Connect; Google: your first Android Package upload must be manual) before EAS Submit's automated path works for subsequent builds — this is a store-side limitation, not an EAS one, and is easy to miss if you skip straight to automation.

Getting a React Native app to compile is table stakes; getting it in front of real users means signed binaries, store listings, review processes, and two very different sets of platform rules. EAS (Expo Application Services) removes the local-toolchain half of that problem — cloud builds mean you don't need a Mac to ship iOS — but the store-side process (metadata, screenshots, review) is still real work. This project walks a real app through both: a cloud build, a submission, and landing in TestFlight and a Play Store testing track.