1. Graphics have strict specs

• App icon: 512x512, PNG or JPEG, up to 1 MB
• Feature graphic: 1024x500, up to 15 MB
• Phone screenshots: 2 to 8 images, PNG or JPEG, up to 8 MB each, aspect ratio 16:9 or 9:16, each side 320 to 3840 px

My screenshots came straight from the device at 2:1, which doesn't fit. Instead of cropping the UI, I scaled them down and padded the sides with the screen's background color to reach 1080x1920.

2. The listing has hard limits

App name 30 characters, short description 80, full description 4,000. I picked the name for search and kept my brand in the developer name.

3. Data safety: "collected" vs "shared"

My app makes one optional network call: weather, using approximate location. Location that leaves the device counts as collected. Whether it is also shared depends on whether the provider counts as a service provider acting on your behalf. I answered conservatively ("shared"), because over-declaring doesn't get rejected while under-declaring can.

4. The privacy policy must match the app

You need a public URL. I host mine on GitHub Pages and updated it when I added the weather feature. The policy, the Data safety answers and the listing text all have to tell the same story.

5. Content rating is a questionnaire

It is an IARC questionnaire and the rating comes from your answers. For a clock with no user-generated content, every answer was "no".

6. Attribution and licences

If you use a data API, read its attribution rules. OpenWeather's free plan asks for visible attribution, and a link buried in a legal page isn't enough. I also ship an open-source licences screen inside the app.

7. Signing and versions

Upload an AAB signed with your upload key. versionCode has to go up with every upload. Keep the keystore out of git.

8. The testing requirement depends on your account

New personal developer accounts may need a closed test with 12 testers for 14 days before production. My account is older and wasn't affected, so check what your own Console dashboard says before you plan around it.

9. Review takes a while

After the first submission the dialog said review usually finishes within 7 days. Later listing changes, like adding translations, go through review too.

What did I miss? If you have shipped an app, I'd like to hear which step cost you the most time.

Originally published on DEV Community: https://dev.to/seo_seo_ee802f09cf450729f/submitting-your-first-android-app-to-google-play-the-paperwork-nobody-warns-you-about-7l4