How to Publish an App on Google Play (2026): Step by Step

The short answer: create a Google Play developer account ($25, once), build your app as an Android App Bundle, create the app in Play Console, fill in the store listing and the App content forms, and send a release for review. If your developer account is a personal one created after November 13, 2023, there is one extra step that surprises most people: a closed test with at least 12 testers for 14 days before Google lets you publish to everyone. Plan on three to four weeks from start to finish.

Everything below comes from Google's Play Console Help pages, checked October 14, 2026.

What you need before you start

• A Google account, $25 on a card that isn't prepaid, and a government ID.
• For a personal account, a real Android phone (Android 10 or later) to confirm with the Play Console app.
• Your app as an Android App Bundle (.aab). Google Play won't take an APK for a new app.
• A package name you're happy to keep forever, such as com.yourname.todo.
• An app icon (512 × 512), a feature graphic (1024 × 500) and at least 2 screenshots.
• A privacy policy on a public web page, and a way to delete accounts if your app has logins.
• A test login for Google's reviewers, if parts of your app need an account.

Step 1: Create your Google Play developer account

Go to play.google.com/console, sign in and choose the account type. Both types get the same features:

• Personal is for individuals, students and hobbyists. You verify with a government ID and confirm you have a real Android phone through the Play Console app. Google shows your legal name, country and developer email on your apps' store pages.
• Organization is for a registered business. It needs a D-U-N-S number (free, but it can take up to 30 days to get), an organization document and a website. Finance, health, VPN and government apps must use an organization account.

You must be 18 or older, and you can't submit apps until verification is done, so start this before your app is finished.

Step 2: Build your app as an Android App Bundle

New apps must be published as an Android App Bundle (.aab), and Google builds the right version for each phone from it. Three things are decided here:

• The package name (applicationId), like com.yourname.todo. It is fixed once you upload the first build, shows up in your Play Store link, and can never be reused.
• The signing key. Play App Signing is required for new apps: Google keeps the key that signs your app for users, and you sign each upload with your own upload key. If you lose the upload key, Google can reset it.
• The Android version you target. Since August 31, 2026, new apps and updates must target Android 16 (API level 36). Expo SDK 54 and later already do.

If you build with Expo, EAS Build produces the .aab and can create and store your upload key for you.

Step 3: Create the app in Play Console

In Play Console, choose Create app. Enter the app name, the default language, whether it's an app or a game, and whether it's free or paid, then accept the declarations. Decide carefully: once an app has been free, it can't be changed to paid. Google's publishing API can't create apps, so every publishing tool, ours included, asks you to do this one step by hand.

Step 4: Upload to internal testing first

Under Test and release → Testing → Internal testing, create a release, upload the .aab and add up to 100 testers (yourself included). You can do this before finishing the app setup, and builds usually reach testers within minutes. The very first test link can take a few hours to work. It's the quickest way to check the real store build on your own phone before anyone else sees it.

Step 5: Fill in the store listing

The store listing is your app's page on Google Play:

Don't put words like "Best", "#1", "Top", "New" or "Free" on your icon, feature graphic or screenshots: Google doesn't allow them. To be eligible for featuring, add at least four screenshots of 1080 pixels or more.

Step 6: Complete the App content section

Policy and programs → App content holds the forms Google needs before a closed test or production. Most take a few minutes each:

• Privacy policy: every app needs one, both as a link in Play Console and as a link or text inside the app. It must be a public web page, not a PDF.
• Data safety: what data the app collects or shares, and why, including data collected by libraries and SDKs. Even apps that collect nothing must fill it in.
• Sign-in details (once called App access): if features sit behind a login, give the reviewers a reusable test account, in English, that won't expire.
• Content rating: a short questionnaire that gives your app its age ratings. Apps without a rating are removed.
• Target audience and Ads: who the app is for and whether it shows ads. Apps aimed at children follow the stricter Families policy.
• Financial features and Health apps: every app answers these, even if the answer is "none".
• Account deletion: if people can create an account, they must be able to delete it from inside the app and from a web page, and you enter that web link in Play Console. Deactivating an account doesn't count.

Step 7: Run a closed test (the 12-tester rule)

If your developer account is a personal one created after November 13, 2023, Google requires a closed test with at least 12 testers who stay opted in for 14 days in a row before you can apply for production. Internal testing doesn't count, open testing stays locked until you have production access, and a tester who opts out and back in starts their 14 days again.

Ask friends, colleagues or early users to join, and make sure they actually use the app. When you apply, Google asks how you found testers, what feedback they gave and what you changed; too few engaged testers is the most common reason it asks you to keep testing.

Step 8: Apply for production and release

After the 14 days, choose Apply for production on the Dashboard and answer Google's questions about your test, your app and how you know it's ready. Google says this review usually takes seven days or less. Once approved, create a production release, choose your countries and send it for review.

Google says processing can take from a few hours up to seven days, longer in exceptional cases, and that new developer accounts can see longer reviews, so leave at least a week before any launch date. Staged rollouts, where an update goes to a percentage of users first, only work for updates, not for your first release.

Where first-time publishers get stuck

• Google Sign-In or Firebase stops working after release. Register the fingerprints of Google's app signing key (Play Console shows them) with those services, not just your own upload key.
• Photo and video permissions. Apps may only ask for broad access to photos and videos if that's their core purpose; most apps should use the system photo picker instead.
• Background features. Background audio, location or other foreground services need a declaration with a short demo video.
• Reviewers can't log in, or the privacy policy doesn't match the Data safety answers.
• Repeated rejections. Google warns that multiple rejections can lead to the app being suspended, so fix every point before you resubmit.

How GenVibe handles most of this for you

GenVibe builds React Native (Expo) apps from a description, and its Publish window walks through the Google Play steps in order:

1. Build the app bundle. The .aab builds on your own free Expo account, so the app and its signing key stay yours. You pick the package name before the first build.
2. Publish to Google Play. After you create the app in Play Console and connect a Google Play key, GenVibe uploads each build to internal testing and emails you when it's there.
3. Store listing. GenVibe drafts the descriptions, makes the icon and feature graphic, takes the screenshots, and sends them to Play Console once you've checked them. It also suggests answers for the App content forms from what your app does.
4. Privacy policy. GenVibe writes a privacy policy and an account-deletion page from what your app does, hosts them, and can add the in-app links for you.

You still create the developer account, run the closed test and press the final release button, because Google requires those from you. Publishing to Google Play comes with every paid plan. Start building free →

Frequently asked questions

Sources: Google Play Console Help on getting started, testing requirements for new personal accounts, store listing graphics, user data and account deletion, target API level and review times, plus Expo's Android submission guide, all checked October 14, 2026. Google updates its rules often; check Play Console for the latest.