How to publish an app on Google Play in 2026 (step by step, no developer needed)
Everything you need to publish an Android app on Google Play in 2026. The account, the fee, the 12 testers rule, Google's review, and the four steps Snapp walks you through.
To publish an app on Google Play, you need a Google Play developer account (a one time 25 USD fee), an Android App Bundle (AAB) file, a store page, answers to Google's policy forms and an approval from Google's review. New personal developer accounts also have to run a 14 day closed test with 12 testers before the app can go public. With Snapp, your part takes about ten minutes: Snapp creates the app in Play Console, fills in Google's forms, uploads your app and follows the review.
Key facts
- Fee: Google charges a one time registration fee of 25 USD, paid by credit or debit card. Prepaid cards are not accepted (Google).
- New personal accounts: personal accounts created after November 13, 2023 must run a closed test with at least 12 testers, opted in for 14 days in a row, before applying for production (Google).
- Review time: for certain developer accounts, Google says reviews can take up to seven days, or longer in exceptional cases (Google).
- With Snapp: publishing needs a paid Snapp plan (Starter or higher). Each store build uses one build from your plan.
- App check: problems that could stop your app from working in the store. If Snapp finds any, tap Fix to see them. You can still release, but Google may refuse the app until they are fixed.
- Store name: the name people see on Google Play.
- App icon: the icon on the store and on the phone.
- Check the text and change anything you like. Your changes are kept as you go.
- Fix anything listed under Still missing. Snapp tells you exactly what is needed.
- Under Snapp's answers, read the answers Snapp gives to Google's forms. If they are right for your app, turn on the switch to agree.
- Press Approve.
- Get started with Play Console (registration fee)
- App testing requirements for new personal developer accounts
- Set up an open, closed, or internal test
- Publish your app
- Prepare your app for review
- Required information to create a Play Console developer account
- Device verification requirements for new developer accounts
What do you need to publish an app on Google Play?
Here is the full list, and who does each part with Snapp.
| What Google needs | What it is | Who does it |
|---|---|---|
| Developer account | Your Play Console account. Your apps are published under it, so they stay yours. | You, once |
| Identity and contact verification | Google checks your legal name and address, and verifies your email and phone with a one time code | You, once |
| Android device check (new personal accounts) | You confirm you have a real Android phone (Android 10 or later) in the Play Console app | You, once |
| App file (AAB) | The file Google Play installs from | Snapp builds it |
| Store page | Name, icon, description, screenshots | Snapp prepares it, you approve |
| Privacy policy | A web page that says what your app collects | Snapp makes and hosts it |
| App content forms | Content rating, data safety, ads, target audience | Snapp answers, you confirm |
| Closed test (new personal accounts) | 12 testers for 14 days | You, in Play Console |
How much does it cost to publish on Google Play?
Google charges 25 USD once, not every year. There is no fee per app. If you sell something in your app, Google takes a share of the sale; that is covered in How much does it cost to publish an app in 2026?.
To publish from Snapp you need a paid plan. Starter is 24.99 USD a month and includes 3 store builds a month (US price as of October 2026; the stores show local prices).
How to publish an app on Google Play with Snapp, step by step
If you do not have a developer account yet, follow How to create a Google Play developer account first.
Open the Publish tab and pick your app. You can also get there from your app's Settings with Publish App. On the Publish card, select the Google Play tab. It is on the left.
The Publish card has four steps. Each one shows who does it: You, Snapp, or Snapp + you.
Step 1: Get your app ready
Snapp checks three things:
Step 2: Give Snapp access to Google Play
You do this once. After that Snapp can publish all your apps.
If Snapp asks Do you have a Google Play developer account?, tap Yes, I have one. Tap No, not yet and Snapp shows you how to make one, with a Create a developer account button.
1. In Play Console, open Users and permissions and press Invite new users.
2. Enter the email shown in Snapp. Under Account permissions, tick Admin (all permissions), then press Invite user.
3. Come back to Snapp and press I invited Snapp.
Snapp looks for your invite. This takes up to a minute. When the step shows Connected, you are done.
If Snapp asks you to confirm your account. Snapp only publishes into a Play Console account that is yours. If the email you use in Snapp is not a user of that Play Console account, tap My Play Console uses another email. Enter the email you sign in to Play Console with and Snapp sends a 6 digit code there. Enter the code and Snapp continues.
Step 3: Store page
Tap Prepare. Snapp writes your store text, takes screenshots and makes your privacy policy. Then:
After approving you can tap Send to Google Play right away. No build is needed for this. Snapp creates your app in Play Console, fills in the forms and adds your store page, so you can see it there. Nothing is released yet.
More about this step: Your store page: what Snapp prepares and what you check.
Step 4: Release on Google Play
First make the file. Tap Build the app on the Build card, pick AAB, for Google Play and press Start build. It takes about 15 minutes. You can close the screen: you get a notification when it is ready.
When the build is ready, tap Release on Google Play and confirm with Send. Snapp uploads it and your app goes to internal testing, so you and your testers can install it first. Internal testing has no Google review.
When you are happy with it, tap Make it public on Google Play. This sends the app to Google's review. You get a notification and an email when your app is live, and the Open on Google Play link appears under On the stores.
What does Google review?
Google checks that your app follows the Developer Program Policy and matches what you declared on the App content page: your privacy policy, whether the app has ads, how reviewers can get into restricted parts of the app, the target audience, the content rating and the data safety answers (Google).
Common problems Google lists: content that breaks policy, a target age group that does not match the app, crashes or broken screens, and missing login details for reviewers (Google). If your app opens with a sign in, add a Demo account on your store page in Snapp.
How long does it take to publish on Google Play?
| Step | Typical time |
|---|---|
| Your part in Snapp (access, store page, release) | About ten minutes |
| Building the app file | About 15 minutes |
| Internal testing | No Google review. Google says internal test builds reach testers within minutes. |
| Closed test (new personal accounts only) | At least 14 days, then Google reviews your production application, usually in seven days or less |
| Google's review to go public | Usually a few days; Google says up to seven days or longer in exceptional cases for certain accounts |
The 12 testers rule for new personal accounts
Google asks personal accounts created after November 13, 2023 to run a closed test with at least 12 testers who stay opted in for 14 days in a row. Only then can you apply for production access from the Play Console Dashboard. Organization accounts are not covered by this rule.
If that applies to you, Snapp tells you when you tap Make it public on Google Play. Start the closed test in Play Console under Testing, then Closed testing, and try again after 14 days. To find testers, join the Snapp community (a WhatsApp group: tap Join Community in your app's options in Snapp, or Community at the bottom of snappai.co): Snapp users test each other's apps there.
What counts as a tester, what resets the 14 days and how the application works: Google Play's 12 testers rule in 2026. Need people? See How to get 12 testers for Google Play without paying.
If Google does not approve it
You see Not approved with Google's reason, for example a privacy policy problem. Fix it on the store page, then release again. If you are not sure what to change, contact us at snappaico@gmail.com.
Refused production access after a closed test? See Google Play production access rejected?.
Frequently asked questions
Do I need to know how to code? No. Snapp builds your app, prepares the store page and sends it to Google. You only create the account, invite Snapp and approve.
Do organization accounts need 12 testers? Google's testing requirement applies to personal accounts created after November 13, 2023. Organization accounts are not covered, but they need a D-U-N-S number.
How do I update my app after it is live? Build again and tap Send update. If you changed only the store text or screenshots, tap Send store page; no build is needed. More in After you release: reviews, updates and builds.
Can I publish the same app on the App Store? Yes. Use the App Store tab on the same Publish card. See Publish your app to the App Store with Snapp.
Ready to publish? Open your app at snappai.co and tap Publish.
Sources
Last updated: October 2026.
Snapp Team
Articles and content from the SNAPP team
