What I Wish I Knew Before Publishing My First Android App

I've published a few small Android apps on the Play Store. None of them are big hits, but each one taught me something the tutorials skip. If you're about to ship your first app, here's what actually slows people down.

1. The closed testing requirement will eat two weeks you didn't budget for

If your Google Play developer account is a personal account created after November 13, 2023, Google will not let you publish to production until you run a closed test with at least 20 opted-in testers for 14 continuous days. This isn't a formality. If a tester opts out or the count drops below 20 at any point, the countdown can reset. Organization accounts are exempt, but most first-time solo developers are on personal accounts and get hit by this.

Plan your launch date around this from day one, not after your build is ready. Google's own guide is the source of truth here, not old blog posts that still mention 12 testers, since the requirement was raised: https://support.google.com/googleplay/android-developer/answer/9842756

1. Your data safety form has to match what your app actually does, not what you plan to add later

Google now runs AI-assisted review on the Data Safety section specifically. If you declare "no data collected" but a third-party SDK you added (analytics, ads, crash reporting) is quietly sending data, that mismatch gets flagged and can delay or reject your submission. Audit every SDK in your build.gradle before filling this form out, not after.

1. A permission with no clear purpose is the fastest way to get rejected

Requesting camera, location, or contacts access without a feature in the app that obviously needs it is one of the most common rejection reasons for new apps. If a permission isn't tied to a visible feature, remove it. You can always add it later when the feature exists.

1. Design for Material You before you touch a single Activity

Skipping Android's design guidelines is invisible in your own testing because you already know how your app works. New users don't. Following Material Design conventions for navigation and spacing means testers spend their attention on your actual feature, not on figuring out where the back button equivalent is. Reference:

1. Your app icon and screenshots do more work than your first week of features

Nobody taps into a listing to read your description first. The icon and the first screenshot decide whether they tap at all. I redesigned my icon after launch and saw a real difference in install rate from the same amount of impressions. Treat this as a real task with its own time budget, not an afterthought before submitting.

1. Review timelines are longer than you think, and resubmission adds more

A clean first submission usually takes 24 to 72 hours to review. If your app has subscription billing or DRM, budget 3 to 7 days. If you get rejected and have to resubmit, add another 3 to 7 days on top. Combined with the 14-day closed test, a realistic timeline from "code complete" to "live" is closer to three weeks than three days.

None of this is advanced Android development. It's the operational side of shipping that nobody mentions until you hit it yourself. If you're mid-way through your first app right now, check your testing track status today, since that clock is the one thing you can't rush later.