Publishing Your First App on a New Google Play Developer Account: A Realistic Timeline

Short answer: plan for about three to four weeks from "app ready" to public release on a new personal account. That covers finishing app setup, at least 14 days of closed testing with 12 or more testers, and a production access review that Google says usually takes seven days or less. Here's the timeline and where people lose time.

Week 0: app setup and internal testing

Finish the Dashboard tasks (content rating, target audience, data safety, store listing basics) so the closed track opens. Meanwhile, share builds through internal testing, which is available immediately and delivers builds within seconds. Start recruiting closed testers now, not later.

Weeks 1 and 2: the closed test

Roll out to the closed track, share the opt-in link and confirm each tester's opt-in date. Run daily tasks, collect feedback and ship fixes. Google requires at least 12 testers opted in continuously for the 14 days before you apply.

Week 3: apply and wait

Apply from the Dashboard with specific answers about your test. Google says review usually takes seven days or less and can occasionally take longer. Keep your closed test running while you wait, in case Google asks for more testing.

Week 4: launch

After approval, Production and Open testing unlock. Prepare your store listing and screenshots, choose a staged rollout if you like, and keep a closed track for future updates.

Where people lose time

Recruiting after setup instead of during it

You lose days waiting for testers.

No buffer

One tester leaves on day 12 and your earliest application date moves two weeks.

Thin engagement

A rejection for low engagement means more testing time.

Missing test credentials

If reviewers can't log in, they can't evaluate the app.

TestLancer's free Google Play Launch Center has an interactive 12-step checklist that follows this order.

The official rules, in one place

According to Google's Play Console Help article on app testing requirements for new personal developer accounts:

• The rule applies to personal developer accounts created after November 13, 2023.
• You must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.
• Production and Pre-registration stay disabled until you meet the requirement; you then apply for production access from the Dashboard.
• The application has three parts: About your closed test, About your app/game and About your production readiness.
• Review usually takes seven days or less, but can take longer. If engagement was too low or you had fewer than 12 opted-in testers, Google may ask you to keep testing.
• Testers who opt out before 14 days don't count, and if someone opts out and back in, their 14 days must be consecutive.

Quick checklist before you apply for production access

• [ ] At least 12 testers opted in today, each for 14 or more days in a row (check your log, not your memory).
• [ ] A buffer of extra testers in case someone drops out at the last minute.
• [ ] Notes on which features testers used, and whether that matched how you expect real users to behave.
• [ ] A short summary of the feedback you received and how you collected it (Play testing feedback, a form, a chat group).
• [ ] A list of changes you made because of the test, with version numbers.
• [ ] Working test credentials in Play Console if your app needs a login.
• [ ] Content rating, target audience and data safety answers that match the real app.
• [ ] No crashes or empty screens on the build you're about to ship.

If any box is empty, a few more days of testing usually costs less than another review cycle.

Mistakes that cost developers extra weeks

1. Recruiting exactly 12. One opt-out and you're back to waiting.
2. Running the test on the internal track. Internal days don't count toward the requirement.
3. Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
4. Tidying the tester list mid-test. Removing someone ends their streak.
5. Shipping no updates. The production readiness section asks what you changed because of testing.
6. Using friends who never open the app. Google can ask for more testing when engagement is low.
7. Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.

FAQ

Can I shorten the 14 days?

No. The requirement is at least 14 continuous days.

Can I prepare the store listing during the test?

Yes, and you should, so you're ready the day access is approved.

Will the timeline be the same for updates?

Once you have production access, you can release updates without repeating the 14-day requirement, though testing first is still wise.

Next step

If you can't find 12 reliable people on your own, TestLancer's Google Play closed testing service runs a 14-day closed test with real testers who opt in, use your app and send feedback you can summarise in your production access application. You can also use the free Google Play Launch Center checklist first. TestLancer does not sell reviews, ratings or installs, and no one can guarantee Google will approve production access. Your app still has to meet Google Play policy.