What Google Play checks on a first release

Publishing on Google Play for the first time involves more than uploading a build. Play Console asks a series of questions about the app, its data and its audience, and the answers have to match what the app actually does. These are the parts we start on early for every Android launch.

Set up the developer account early

Google verifies the identity behind every developer account. Organization accounts need a D-U-N-S number, and the details you enter have to match it. Verification can take a while, so start before the app is finished. It shouldn’t be the last thing holding up the release.

Know which testing rules apply

Play Console has three testing tracks: internal, closed and open. Newly created personal developer accounts must run a closed test, with a minimum number of testers for a minimum period, before they can apply for production access. Organization accounts aren’t subject to that rule, but a closed test is still worth running. Check the current requirements in Play Console when you plan the schedule, because they have changed before.

Make Data safety and the privacy policy agree

Every app on Google Play needs a completed Data safety section, even one that collects nothing. It describes what data the app collects and shares, why, and how it’s protected. Include what your SDKs collect: analytics, crash reporting and advertising libraries all count.

The app also needs a privacy policy at a public URL, entered in Play Console and easy to find inside the app. It should describe the same data the Data safety section does. A generic template that mentions none of your actual data won’t hold up, and a mismatch can lead to a rejection or a policy warning later.

Offer account deletion in the app and on the web

If people can create an account in your app, they must be able to request its deletion from inside the app. Google also asks for a web page where people can request deletion without reinstalling the app. Both should say what is deleted, what is kept and for how long.

Target a recent API level

Google Play requires new apps and updates to target a recent Android API level, and the minimum moves up every year. A project started from an old template, or paused for a few months, can fall behind without anyone noticing. Check the target before the first upload rather than after a rejection.

Answer the app content questions

Play Console also asks about content ratings, the target audience, ads, and how a reviewer can get past any login. If the app needs an account, provide working test credentials with the data the reviewer needs to see. If children are part of your target audience, extra policies apply, so settle that question carefully and early.

The short version

Start account verification early, plan for the testing your account type needs, and make the Data safety section, the privacy policy and the app tell the same story. Allow extra time for the first review. Updates are usually quicker once the app is live.