Publishing a React Native App on Google Play
Publishing on Google Play
~12 Min. Lesezeit Zuletzt aktualisiert am August 8, 2026
This chapter walks you through the complete path from a finished app to publishing it on Google Play – including the costs and the registration process.
Creating a Google Play Console account
Register at play.google.com/console with a regular Google account. Cost: a one-time 25 US dollars, no annual fee (unlike Apple). Google also now requires identity verification (ID/address proof) as well as a short "testing program" period with at least 12 testers over 14 days before an app becomes fully publicly visible ("Production") – this applies to new developer accounts since 2023.
Building the app: EAS Build
Instead of building locally with Android Studio, publishing usually uses Expo's cloud build service "EAS Build" (Expo Application Services) – it produces a finished, signed .aab file (Android App Bundle) without you having to manage a full local Android SDK with all its signing certificates:
npm install -g eas-cli
eas login
eas build:configure
eas build --platform android --profile productionEAS Build has a free tier (limited number of builds per month, usually enough for learning and hobby projects) as well as paid subscriptions for higher build frequency and priority in the queue.
Creating the store listing in Play Console
- App name, short description, full description (in German AND English if you want to offer multiple languages)
- At least 2 screenshots per supported device category (phone, optionally tablet)
- A store icon (512×512 px) and a feature graphic (1024×500 px)
- Privacy policy URL – a required field; even free apps that collect no data must link a (even minimal) privacy policy
- Content rating (an age-rating questionnaire, automatically generated from your answers)
- Target audience and content declarations ("Content rating", "Data safety" form about data collected)
Uploading and review
The .aab file is uploaded in Play Console under one of the release tracks ("Internal testing" for fast internal tests with no wait, "Closed testing", "Open testing", or directly "Production"). Google's review process usually takes a few hours to 2–3 days – noticeably faster than Apple.
Tipp: "Internal testing" is the fastest way to share a build with family/friends without waiting for the full review: invite testers via an email list, they receive a link, and install the app directly through the Play Store as a "tester" – usually available within minutes of upload.
Google Play cost overview
| Item | Cost |
|---|---|
| Google Play Console account | $25 one-time |
| EAS Build (free tier) | $0 (limited builds/month) |
| Publishing the app itself | $0 (no store fee for free apps) |
| For paid apps/in-app purchases | 15–30% commission on revenue (tiered by annual revenue) |