Blog
What I Learned Shipping My First Apps on Google Play
When I started PARqore, I thought writing the app would be the hard part. It wasn’t. The hard part was everything between “it works on my phone” and “strangers can install it from Google Play.”
I’m a solo founder in Hendersonville, North Carolina, and I’ve been building Android apps for about six months. My first app, New Life Daily, reached Google Play production, followed by FarmSeconds and ColorDrop. A few others are still working through testing. Here’s what I learned getting there.
1. Plan for about a month, even if your app is finished
For a brand-new personal developer account, the clock isn’t yours. Identity verification takes days, review takes hours to days, and then there’s the big one:
2. The 12-tester, 14-day rule
Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before they can apply for production. FarmSeconds got production access on September 29, and I still had to create the production release, send it for review, and roll it out after that.
The trap I fell into: adding someone to your tester list doesn’t make them a tester. They have to open your opt-in link while signed into that same Google account and tap “Become a tester.” If you use a Google Group, they join the group first. The only number that matters is the opted-in count in Play Console. Aim for 15 or more so one dropout doesn’t reset your progress.
3. Warn your testers before they leave
When I left the test for one of my own games on my phone, the app was uninstalled and my save was gone. Google’s pages don’t spell this out, so treat it as one developer’s experience. Since then, I tell every tester: please don’t leave the test until the app is live.
4. Your privacy policy, Data safety form, and app have to agree
Every app on a closed, open or production track needs a Data safety form, even if it collects nothing, and you’re responsible for what your third-party SDKs collect too. Before touching the form, I write a simple worksheet (data type, collected? shared? why? optional?) and check each line against the code.
5. versionCodes only go up
Every upload needs a versionCode higher than anything you’ve ever uploaded for that app, on any track, even builds that were rejected. Some build services assign their own codes, so I check Play Console before every upload.
6. Test the release build, not just the debug build
An R8 setting broke one of my release builds that worked perfectly in debug. My rule now: never upload a build I haven’t installed and opened on a real phone in release mode.
7. Little things that cost me time
- Phone screenshots can’t be more than 2:1, and my phone’s native screenshots were taller; cropping to 1080×2160 fixed it.
- Feature graphics can’t have transparency.
- Changes don’t go to review on their own: check Publishing overview and click Send for review.
- Free email forwarding from my domain registrar gave me [email protected] without paying for a mailbox.
Want the whole thing?
I turned all of this, plus copy-paste tester invites, reviewer access notes, and links to every official Google page I used, into a 35-page field guide: Ship Your First Android App on Google Play, $17. There’s also a Play Store Launch Kit ($12) and an App Launch Tracker spreadsheet ($12), or all three for $29.
If you just want the short version, grab the free one-page checklist.
And if you get stuck, email me at [email protected]. I can’t promise I’ll know the answer, but I’ll tell you what I’d try.
Not affiliated with or endorsed by Google. Google Play and Android are trademarks of Google LLC. Policies change, so always check Google’s official help pages.