(... so far)

I’m writing this partly as a reference for myself and partly because I wish I had found something like this before starting. It’s not a polished guide, just a checklist of things I’ve learned, struggled with, or stumbled across while trying to publish my first app.

Checklist

  • Exporting your app
    Learn how to export to .apk and sideload your app. This avoids having to upload an .aab and wait for Play approval every time you make a small change.

  • Use a dedicated Gmail account
    Create a brand new Gmail account before you begin. I strongly suggest using it (and Google’s built-in authentication) for all the other accounts you’ll need. Technically not required, but it gives you a central spot for communication plus a little Google Drive storage you can use for documents, pictures, etc.

  • Google Play Console Developer account

  • Costs $25 to register (non-refundable).

  • You’ll need to enter some personal information just to register.

  • You’ll need even more information if you plan to sell your app or offer in-app purchases.

  • Closed testing requirement
    You must run a closed testing period before you can publish on the store. This requires at least 12 people to opt in, download your app, and keep it installed for 14+ days.

  • Google Merchant account
    If you plan to have purchases (in-app or charging for the app), you’ll need a separate Google Merchant account.

  • Google Payments profile
    Required to get paid through your Merchant account (at least I think this one is required).

  • Google AdMob
    If you plan to use Google’s ads, you’ll need another account. AdMob is not the same as AdSense.

  • Google Group for testers
    Creating a Google Group for your testers really helps manage onboarding and feedback.

  • Store graphics
    You’ll need images, icons, and feature graphics. Get used to using a screenshot tool and basic image editors. (I’m not good at image creation, but I can crop/resize and add some text — you should be able to, too.)

  • Questionnaires
    Be ready to answer questions about your intent on the platform:

  • What kinds of apps do you plan to make?

  • How many per year?

Be ready to answer similar questions about your app itself:

  • Who is your target audience?

  • Is there gambling?

  • Do you have ads?

  • Do you have in-app purchases?

  • App scanning & delays
    Google scans your app (and every update you upload). This can cause delays — just be mindful and patient.

  • Tester eligibility
    You can count as a closed tester yourself if you created a separate Google account for the Play Store in addition to your personal account.

  • Privacy policy
    Even if you collect zero data, have no ads, and don’t intend to collect data, you should still publish a privacy policy stating so. If you do any of those things, a privacy policy is a requirement.

  • Feedback from Google
    Google will give feedback, suggestions, and notifications. For instance, my app was targeting an older Android platform. After updating, Google acknowledged I had fixed it. Take their feedback seriously — I’d imagine it factors into their production access consideration (though I can’t verify that).

  • Community tip
    There’s a subreddit — r/AndroidClosedTesting — where developers will test your app during closed testing if you test theirs.

This is by no means an exhaustuve (or finished) list, as I'm not finished getting published yet! Let me know in the comments what I'm missing (especially any big hurdles I missed).