What it actually takes to publish your first app on Google Play
The code was done. Luna Journal recorded, transcribed and titled an entry, the whole thing ran on the phone and I sat there feeling like the hard part was behind me. Then I started trying to publish my first app on Google Play and it turned out the build was the easy half.
I'm writing this from the middle of it, with three apps lined up for the Play Store rather than one shipped and done, so treat it as a field report and not a victory lap. If you're about to publish your first app on Google Play on your own, here's what the process actually involves in 2026 and where the time really goes.
The 25 dollars and the account are the simple part
Setting up a developer account is the bit people warn you about and it's genuinely fine. You pay Google a one-off 25 US dollars, confirm who you are and you're in. There's an identity check now, your name, your address and sometimes a document, which took a couple of days to clear for me, so start it early rather than the week you want to launch. After that you create the app record in Play Console: name, default language, free or paid, app or game. Ten minutes. If the whole thing were this calm I wouldn't be writing a post about it.
The closed testing gate: 12 testers for 14 days
Here's the part that caught me out. If your developer account is a personal one created after November 2023, which mine is, you can't just send your app straight to production. Google makes you run a closed test first. At least 12 testers, opted in and staying opted in, for 14 straight days, before you're even allowed to apply for production access.
It used to be 20 testers. They dropped it to 12, which helps a bit, but the shape of the problem doesn't change. You need a dozen real people with Google accounts, willing to install a half-finished app and leave it on their phone for two weeks and you need them before anything is public.
The 14 days are a floor, not a countdown you can hurry. Google wants those 12 testers opted in across the whole fortnight, so if three of them lose interest on day five and uninstall, you can quietly slip under the line without noticing. And clearing the bar doesn't guarantee approval. Google still asks what you changed during testing and whether real people actually used it, then reviews the app on top of all that.
Finding 12 testers when you build alone
This is the part that's genuinely hard for a solo developer and nobody really counts it in when they picture just shipping the thing. Twelve people is nothing for a company with a team and a mailing list. On your own it's your group chat, a couple of forums, your family and whoever you can talk into it.
I leaned on friends, a small Android testing community and, honestly, a bit of begging. A few things that helped:
- Ask for more than 12. Some people opt in and never open the app again, so aim for 15 or 16 to stay safely above the line all fortnight.
- Make opting in one tap. Send the Play test link directly, with a single sentence on what to try, not a wall of setup instructions.
- Be clear it's two weeks on the phone, not two weeks of work. People say yes far more readily once they know you just need the app installed, not a daily report.
The store listing is a project of its own
While the 14 days tick along there's a surprising amount of writing and form-filling waiting for you. A listing needs a title, a short and a full description, a feature graphic, screenshots at the right sizes and an icon. Then come the declarations: a content rating questionnaire, a data safety form, a target audience section and a privacy policy you have to host at a real URL.
This part was easier for me than it is for most, because Luna keeps your entries on your device and I don't run servers that hold them, so the data safety form was mostly a list of no. If your app sends data off the phone, expect that form to take real thought, because it's a public promise you're then held to.
Why it takes longer than the number suggests
Add it all up and 14 days is the optimistic version. The honest timeline looked more like a few days to get testers in, then the 14 days of testing where you're also fixing whatever they find, then production review once you finally apply, which can be anything from a few hours to about a week. Any substantial change can effectively send you back to re-test. So the gap between the app works and you can actually publish your first app on Google Play was closer to a month for me than the two weeks on the box.
The build is the part you control. The store is the part you wait on, so start it earlier than feels necessary.
None of this is really a complaint. The testing gate exists because the Play Store was drowning in junk from throwaway accounts and a two-week speed bump filters out a lot of that before it reaches anyone. It just isn't the part people mention when you set out to build an app on your own, so it's worth planning for from the start.
If you're at the beginning and about to publish your first app on Google Play: open the account and start the identity check now, line up your testers before you think you need them and treat the store listing as its own small project rather than an afternoon's admin. I've since taken Luna Journal, annote and Meridian Clock through it, and the advice above held up. Good luck with yours.
More from the devlog.
How to take hair loss progress photos you can actually compare
Most hair loss progress photos can't be compared because the light, angle and hair change every time. Here is the setup that makes them comparable: four angles, soft daylight, dry hair, once a week.
Does Oura track your alcohol intake? What a ring can and can't do
Your Oura ring or Whoop can show you what a night of drinking cost you, but it can't count what you actually drank. Here is the difference, and how to track your intake properly.