Google charges $25 to open a developer account, once. For a new personal account that is the cheapest part of getting an app onto Google Play. Before the first production release, the account has to run a closed test with 12 testers opted in for 14 days in a row, then answer Google's production access questions. That part costs money, your time, or both, depending on how you do it. Below is each route with its numbers. We sell two of them, so weigh those accordingly.
The fixed costs
The developer account is a one-time $25 payment, made by card when you register. It covers every app you publish from that account, and there is no yearly renewal. Apple, for comparison, charges $99 a year. Google verifies your identity, and new personal accounts are also asked to show they have a real Android device, through the Play Console mobile app.
If you charge for the app or sell anything inside it, Google keeps a service fee on each sale. That is a cost of selling rather than publishing, so it is left out here.
There is one way around the closed test: organization accounts do not need it. They need a registered business and a D-U-N-S number, which is free but can take a while to issue. If you already have a company, that may be the cheapest route of all.
The closed test, four ways
Google counts 12 testers opted in for 14 continuous days. If the count drops below 12, the 14 days start again once you are back at 12. Every route below trades money against the hours you spend recruiting, reminding people and taking notes.
Friends and family
$0. The cost is your time and the drop-out risk. You need 12 people with a Google account and an Android phone who will opt in, install and keep the app for two weeks, and it takes more than 12 names to end with 12. You collect their email addresses, add them in Play Console, remind them, and turn whatever they say into notes for the questionnaire. Friends are kind about your app, which makes the feedback questions harder to answer.
Swap groups
Also $0, paid for in your own testing hours. You install other developers' apps and open them for two weeks in return for them doing the same with yours, often a dozen apps or more. The weak spot is engagement. Swap partners need your install for their own count, not your app, and "testers were not engaged with your app" is one of the two reasons Google's refusal email lists. If you go this way, give partners a short list of tasks and keep a record of who did them.
A paid closed test
A service recruits the testers and deals with drop-outs. Prices run from about $15 to $40 per app as of October 2026. Ours is $39.99 for 16 testers (Standard) or $49.99 for 20 (Pro), both for 14 days and both with the same promise: 12 still opted in on day 14, or the test runs again free. Testers confirm their install before their days count and write notes on day 7 and day 14, and your campaign page drafts production access answers from those notes. You still add the testers in Play Console, write the steps you want them to follow, read the notes, make the fixes, and finish the store listing, the App content forms and the questionnaire yourself.
Done for you: TestFi Launch
$499 for one Android app. It is the 20-tester closed test with the same day 14 promise, plus 5 screen recordings by invited TestFi Pro testers on days 2 to 5, each 15 to 20 minutes of the tester thinking out loud. You get a fix list ranked by severity, with timestamps, by email within 5 business days of the last approved recording. A person reviews your launch checklist (store listing, screenshots, data safety, content rating, target API level, privacy policy, reviewer access, ads, countries) on days 12 to 14. The production access answers are drafted from your testers' notes and edited by a person, and they are on your campaign page within 2 business days after day 14. You read them and submit them. At most 2 Launches start a week, so you may wait for a slot.
Side by side
Google's $25 fee comes on top of every row.
| Route | Money | Your time | What you still do yourself |
|---|---|---|---|
| Friends and family | $0 | Recruiting more than 12 people, two weeks of reminders, notes | All of it: recruiting, replacing drop-outs, collecting feedback, the forms and the answers |
| Swap groups | $0 | Two weeks of opening other developers' apps, plus the above | All of it, and showing that testers used your app |
| TestFi closed test | $39.99 for 16 testers, $49.99 for 20 | Setup, adding testers in Play Console, reading notes | Fixes, the store listing and App content forms, editing and submitting the answers |
| TestFi Launch | $499 | Setup, a short brief for the recordings, the fixes | Fixes, ticking the checklist, reading and submitting the answers |
The time it takes, whichever route
The 14 days are fixed. Before them, every tester has to be added in Play Console and install the app, and after them Google reviews your application. In 112 TestFi closed tests up to 1 October 2026, the median from publishing a test to the 12th confirmed install was 2.6 days. Add the 14 days and you can apply after about 17 days, and Google says its review usually takes seven days or less. If you recruit by hand, the first stretch is however long it takes you to find 12 people. The free closed testing tracker counts the days and shows the earliest date you can apply.
Then there is the questionnaire: nine questions about how you found testers, how they used the app, what they said and what you changed. With notes kept during the test, it is an evening's work. Without them you are writing from memory, and it reads that way.
What a refusal costs
If Google answers "More testing required to access Google Play production", the email asks you to test with closed testing for an additional 14 days with real testers before you apply again. That is another two weeks, another review of up to a week, and whatever the second run costs you: more favors from friends, another round of swaps, or another paid test.
Our closed test plans run again free if fewer than 12 testers are still opted in on day 14, and also when Google's refusal names tester engagement and fewer than 12 testers wrote check-in notes that show real use. One free re-run per closed test, under the closed test terms. Launch goes wider. If Google answers "more testing required" for any reason and you forward the email within 7 days of the end date, the closed test runs again once, free. One re-run per Launch, never a refund, under the Launch terms. On every route, ours included, Google decides production access.
Which one fits
If you have a dozen friends with Android phones who will really open the app, start there and keep notes from day one. If two weeks of chasing people is worth more to you than $39.99, the 12-tester closed test is the cheaper trade. TestFi Launch is for when you also want the recordings, the fix list and a person checking your listing and your answers before you apply.
Frequently asked questions
How much does it cost to publish an app on Google Play?
$25, once, for the developer account. A new personal account also has to pass a closed test with 12 testers for 14 days before it can publish. That costs $0 if you recruit the testers yourself, $39.99 or $49.99 for a TestFi closed test, or $499 for TestFi Launch, which adds screen recordings, a fix list and production access answers edited by a person.
Is the Google Play developer fee paid every year?
No. It is a one-time $25 payment that covers every app on the account. Apple's developer program, by comparison, costs $99 a year.
Do organization accounts need 12 testers?
No. The closed test requirement applies to personal developer accounts created after November 13, 2023. Organization accounts are exempt, but they need a registered business and a D-U-N-S number.
How long does it take to publish a new app on Google Play?
For a new personal account, plan on about three weeks if nothing goes wrong: a few days to get 12 testers installed, 14 continuous days of testing, then Google's production access review, which usually takes seven days or less. A "more testing required" answer adds another 14 days and another review.
Can I pay to get production access?
No. You can pay for testers, recordings and help with the application, but Google decides production access, and no service controls that decision.