Mobile Apps7 min read|20 June 2026

How to Publish an Android App on Google Play in Australia

Publishing an Android app on Google Play in Australia involves more steps than most developers expect, and one requirement stops many new accounts before they even start.

The Requirement That Catches Everyone Off Guard

When you create a new Google Play developer account, Google requires you to complete a closed testing period before your account can publish apps publicly. Specifically, you need at least 12 real testers to remain active on a closed testing track for 14 continuous days.

This is not a one-time checkbox. If your active tester count drops below 12 at any point during those 14 days, the clock resets to zero. Many developers only discover this after their first submission is rejected or delayed.

The requirement applies to all new personal and organisation accounts. Existing developer accounts created before the policy change are not affected, but anyone setting up fresh today needs to complete this process.

Setting Up Your Closed Testing Track

Before you can invite testers, you need a complete app build uploaded to Google Play Console. The build does not need to be your final production version, but it must pass basic policy checks and be a valid APK or AAB file.

Once your build is uploaded, navigate to Testing in Google Play Console and create a closed testing track. From here you can create a tester list and generate an invite link. Each tester needs to accept the invite and then download the app from the Play Store, not from a direct APK.

This last point matters. Google monitors whether testers are downloading and using the app through the official Play Store channel. A direct APK install does not count toward your tester quota.

The 14 Day Window and Why It Resets

The 14-day count begins once you have at least 12 active testers. Active means the tester has accepted the invite, downloaded the app, and Google considers them engaged with the testing track.

If a tester removes the app, closes their account, or otherwise becomes inactive, your count can drop below 12 and the window resets. Daily monitoring is essential. You cannot check on day 13 and hope for the best.

For most development teams without an existing network of Android users, finding and managing 12 real people across 14 days is the primary challenge. The testers need genuine Google accounts on real devices, not emulators.

What Comes After the 14 Days

Once 14 days are complete with 12 or more active testers, you can apply for production access in Google Play Console. Google reviews your application and typically responds within a few days.

Approval grants your account the ability to publish apps publicly on Google Play. From that point forward, the testing requirement does not apply to subsequent apps on the same account.

It is worth noting that Google may also request additional information about your app or business during the review. Having clear app descriptions, a privacy policy, and a support contact address in place before you apply reduces delays.

Getting Help With the Testing Process

For businesses and developers who do not have a ready pool of 12 Android users available, the most practical option is to work with a team that manages this process professionally.

ComTeam handles the complete closed testing process, including tester recruitment, daily monitoring, and replacement of any inactive testers. Once the 14 days are complete, we confirm compliance and you can proceed with your production access application.

If you are also building the app itself, combining development and testing through one partner means less coordination overhead and faster time to launch.

Related Services