How long it really takes to get an app onto Google Play.
Building it is the quick half. Here is the sequence a new app goes through in 2026, taken from our own — including the parts that cost us days.
The question people ask about an app is rarely what it will do. It is when it will be on their customers' phones. The honest answer depends far less on the build than on the gates Google puts between a finished app and the Play Store — and at one of them, the calendar is the only thing that moves you forward.
We know because we are going through them now. Zgjedhja Ime, the rental platform we run in Tirana, was uploaded to Google Play for the first time on 8 September 2026, under a personal developer account. Everything below is either from Google's own help pages or something that happened to us, and we say which.
The short answer
For a new personal developer account, the floor is about three weeks — even if the app is finished on day one.
| Step | How long | Source |
|---|---|---|
| Store listing, content rating, data safety form | About a day of work | Ours |
| Review of the first closed-testing release | Hours | Ours — approved the same day it was sent |
| Twelve testers, opted in for fourteen days in a row | 14 days minimum | Google's rule for personal accounts |
| Review of your application for production | "Usually seven days or less" | Google's help page |
Fourteen days plus a week of review comes to three weeks only if all twelve testers are ready the day the test opens. They rarely are, and every day spent finding them is added to the front of the fourteen.
What the twelve-tester rule actually asks for
It applies to personal developer accounts created after 13 November 2023, and it asks for "a minimum of 12 testers who have been opted in continuously for at least 14 days" before you can apply for production. Three consequences follow, and all three catch people out:
- The clock is per person. Each of the twelve needs fourteen unbroken days. Someone who joins on day ten is not done until day twenty-four.
- Leaving resets it. A tester who opts out and back in has to start their fourteen days again.
- Organisation accounts are exempt. If you are a company, open the developer account as an organisation and the rule does not apply. That needs a D-U-N-S number, which is free but not instant.
When you do apply, Google asks how you recruited your testers, which features they used and what feedback they gave. Twelve names who never opened the app are a weak answer to those questions.
Where it cost us days
1. A build from June was not good enough in September
Google raises the Android version apps must target every year, and refuses uploads below it. From 31 August 2026, new apps and updates must target Android 16 — API level 36. Our first build had been made in June and targeted 35. It was a complete, working app, and Play would not take it until it was rebuilt.
2. The form wanted a page we did not have
If an app lets people create an account, Google requires a way to delete it inside the app and a web page where anyone can ask for their account and data to be deleted — including people who have already uninstalled. We had no such page. We wrote one in all three of the site's languages, saying what gets deleted, what has to be kept and for how long. Then we changed its address in the form after submitting, and the review started again.
3. The data safety form has to describe the app you built
The form asks what the app collects and who it shares it with, and the answer has to come from what the app actually does. Ours has a chat that sends messages to an AI provider, and analytics that report to Google and Meta. All of that is declared. A form that says "no data shared" for an app that shares data is exactly what the review exists to catch.
4. Testers who could not find the app
Two things confused the people we invited, and neither is a fault. While an app is in testing it does not appear in Play Store search at all — not even for its own testers, who reach it only through the testing link. And a phone whose Play Store is signed in to an account that has not joined the test is told the app is not available for this account, or simply Item not found. Both look like something is broken. Both mean the same thing: the account on that phone is not a tester yet.
5. Changing how testers join is reviewed too
Testers come either from an email list or from a Google Group — one or the other, not both. We moved from a list to a group, so people could join by themselves instead of sending us their address. That change went to review as well. Play said reviews typically take up to seven days; this one was approved in about twenty minutes. Plan for the seven.
What to send every tester: use your phone, and the Google account its Play Store is signed in to. Join the group if there is one, open the testing link, press Become a tester, then install from that link — not from search.
How to plan around it
- Find the testers before the build is finished. Twelve people with Android phones and their own Google accounts, who will stay in the test for a fortnight: staff, family, regular customers. Ask them before you need them.
- If you are a registered company, sign up as one. An organisation account skips the tester rule entirely. The D-U-N-S number takes time of its own, so start on it early.
- Target the current API level from the start, and expect to rebuild at least once a year. An app is not a thing you ship once.
- Ask whether you need an app at all. For most small businesses a fast mobile site does the same job with none of this. We wrote down when you should not have one.
What we are not claiming
Our app has not finished this process. At the time of writing it is in closed testing and we are still gathering testers, so we cannot yet tell you how long our production review took — only what Google says it usually takes. When it happens, the number goes here.
Nor is any of this about Apple. We have not shipped to the App Store, and its process is different enough that borrowing Google's timeline for it would mislead you.
Thinking about an app?
Send us the site. We will tell you whether wrapping it is worth doing, what the review is likely to pick up on, and how long it will really take — fourteen days included.
Mobile apps