To put a finished app on the Play Store, you make a Google Play developer account, prepare your app file, fill in your store page, run a 14-day test with 12 testers, and then apply to publish. If your developer account is a new personal one, the test is the step that takes the longest.
Most people are surprised by that test. It is not a bug in your app and it is not a mistake in your account. It is a rule Google added for new developers.
Here is every step in order, with the real screens you will see.
Updated September 2026
Step 1: Make a Google Play developer account
This is the account you publish from. It costs US$25, paid once, not every year [1].
You will pick one of two types.
- Personal. For one person publishing their own apps. Most first-time developers pick this.
- Organisation. For a registered business. Google asks for business details to prove the company is real.
The type matters more than it looks, because it decides whether you need the 12-tester test later. Our developer account guide covers the choice in detail.
Step 2: Get your app file ready
Google does not take the app you run on your phone while building it. It takes a special upload file called an Android App Bundle, which ends in .aab.
Your building tool can make one for you. Look for an option called release build, build bundle, or export for Google Play. The file has to be signed, which your tool also handles.
If the name is new to you, we explain it simply in what an AAB file is.
Step 3: Fill in your store page and the forms
This is the part people see, plus a few questions Google needs answered first.
- Your store page. App name, a short description, a longer description, an icon and screenshots.
- A privacy policy link. A web page explaining what your app does with people’s information.
- Content rating. A short questionnaire about what is in your app. Google turns it into an age rating.
- Data safety. What information your app collects and shares. Answer it honestly, because Google checks it against the app.
- Target audience. Who the app is for, including whether it is aimed at children.
None of this is hard. It is just a list, and the Play Console shows you what is still missing.
Do you need the 12-tester test?
It depends on your developer account, not on your app.
Google’s rule is that personal accounts created after 13 November 2023 must run a closed test with at least 12 testers who stay opted in for 14 days in a row before the app can go public [2]. Organisation accounts do not have to.
Step 4: Run your closed test
A closed test means a private version of your app that only the people you invite can install.
In the Play Console you open Testing, then Closed testing, and upload your app file as a new release.
Then you add your testers’ email addresses and send them the invite link. Each tester has to open the link and accept it. Adding an email alone does not count.
Two things make the 14 days go smoothly.
- Invite more than 12. If one person leaves partway through, you still have enough.
- Ask them to open the app regularly. Google asks what your testers told you when you apply, so you need people who actually use it.
If you do not know 12 people with Android phones, you are not alone. We cover the options in what to do if you do not know 12 Android users, and how to invite testers properly.
Step 5: Apply to go public, then publish
Once your 14 days are done, the Play Console lets you apply for what Google calls production access. That just means permission to make the app public.
The application has three short parts: your closed test, your app, and whether it is ready.
Answer with real details from your test. Our guide to the production access questions shows what good answers look like.
Google says its review usually takes seven days or less, but can occasionally take longer [2]. You get an email either way.
After approval you create a release on the Production track, and your app goes through a normal app review before it appears in the store. Google says that review can take up to seven days, or longer in rare cases [3].
What if Google says no?
You get a different email, and it tells you what to do next.
Google lists the usual reasons: testers did not really use the app, feedback was not acted on, or the application answers were too thin. Then it asks you to test for an additional 14 days with real testers before applying again.
So a refusal costs you another two weeks. That is why it pays to get the first test right. Our post on what to do after a rejection walks through it.
What trips people up
- Adding emails and stopping there. Testers only count once they accept the invite.
- Inviting exactly 12. One person dropping out puts you below the minimum.
- Testers who install once and never return. You will have nothing to write when Google asks what they said.
- Using your own phone with several accounts. Google wants real people. We explain why in can I use my own phone as a tester.
Frequently asked questions
How do I put my app on the Play Store?
Make a Google Play developer account, prepare your app as an .aab file, fill in your store page and forms, run a closed test if your account needs one, then apply for production access and publish. New personal accounts need a 14-day test with 12 testers first.
How much does it cost to put an app on Google Play?
Google charges a US$25 registration fee, paid once. There is no yearly fee for the developer account.
How long does it take to get an app on the Play Store?
For a new personal account, plan for about three to four weeks. The closed test takes 14 days, Google’s review of your application usually takes up to seven days, and the app review can take up to seven more.
Why is Google asking me for 12 testers?
Because your developer account is personal and was created after 13 November 2023. Google requires those accounts to test with at least 12 people for 14 days in a row before publishing. Organisation accounts do not have this rule.
Can I skip the 12-tester test?
Not on a new personal account. The only way around it is an organisation account, which needs a registered business.
What happens after my 14 days are finished?
You apply for production access in the Play Console. Google reviews it, usually within seven days, and emails you. If approved, you publish on the Production track.
If finding testers is the hard part
Option 1: verified testers assigned to you
- Starter, $15 gives you 15 verified Android testers for the full 14 days.
- Pro, $25 gives you 25 testers, plus a detailed ASO report and priority support.
- Testers opt in within 6 hours, so your 14 days start today.
- Verified real Android devices, never emulators.
- Full 14-day retention. They keep using your app for the whole test.
- Automatic tester replacement if anyone goes quiet.
- A feedback report at the end, plus help with the production access questions.
- Production-access guarantee. Approved, or your money back.
This is what we do, and we are the best at it. We have been helping developers through Google Play closed testing since March 2024, longer than most services in this category. Opt for a plan when you are ready.
Option 2: join a free Pack of 16
The Testers Community app puts you in a group of 16 developers who test each other’s apps for 16 days. Anyone who stops testing is replaced.
For the full detail on every screen, see our complete publishing guide.
