Counting Back From the Launch Date Leaves a Column Empty
A schedule built backwards from a launch date tends to hold development time and nothing else, because that is the number the build team can give you on the spot. An app does not open the moment it is finished. Google's Play Console help states that app changes take anywhere from a few hours to seven days to publish, and longer in rare cases. The same document asks you to leave at least a week between submission and release.
Waits in that rare category kept surfacing among developers through August and September 2026. If you are contracting out an app with a fixed launch date, this wait needs a column of its own, counted apart from development. Pushing the build team does not shorten it.
The Seven Days Come With Conditions
Google does not guarantee a review window. The publishing help says that for user protection, apps from some developer accounts get a closer look. Review then takes up to seven days, and longer in rare cases. Updates to an app already on the store work the same way. Standard publishing, the default, processes updates as quickly as possible, but some apps move into extended review and spend the same stretch there.
The help gives an app submitted from a new developer account as one example of what can land in extended review. For a company shipping its first app, treating that number as the baseline rather than the ceiling is the safer read.
What 17 August and 16 September Left on the Record
On 17 August 2026 the official X account for the Google Play business community replied to a developer's question, saying reviews were running longer than usual at that moment and could exceed seven days in rare cases. The reply did not say what had backed up or when it would return to normal.
A month later, on 16 September, Daniel Gultsch, who builds the XMPP messenger Conversations, posted a console screenshot. An update submitted on 9 September had sat in the review queue for a week. Gultsch wrote that the app had been on Play for more than twelve years and ships an update once a month. He added that he understood the queue to be clogged with low quality apps churned out by AI. Google has not named that as the cause. A Hacker News thread on the post went up the same day.
A long running app did not get to skip the line either. When one update takes a week, the build that fixes a bug found right after launch also reaches users a week later.
A New Personal Account Puts 14 Days of Testing First
A personal developer account created after 13 November 2023 has to run closed testing before the app can go public. Applying for production access requires at least 12 testers who have stayed opted in continuously for the previous 14 days. Google usually finishes reviewing that application within seven days, though it can take longer. Where something is short, such as the tester count dipping below 12, the answer that comes back may be to keep testing.
The arithmetic runs like this. Fourteen days of testing plus seven days of access review is three weeks. The release build that goes up afterwards still passes through the review described above. Open a fresh personal account in the client's name and these conditions apply exactly as written. Who creates the account and who holds it belongs on the list of things settled before development starts.
Managed Publishing Separates Approval From Release
With managed publishing turned on, an update still goes through review as usual, but the developer picks when it goes live once it is approved. The help describes this as useful for pushing an update at a specific hour to match an ad campaign or a launch event. It says the same feature helps apps under extended review. With the launch date fixed, you clear review ahead of time and press the button that day.
Apple in a Day, Google in a Week
Apple's developer site states that on average 90% of submissions are reviewed within 24 hours. Launching on both stores the same day means the submission date follows the Google calendar, the slower of the two. The delay Google acknowledged on 17 August turned up again as a week long wait on 16 September.
We Start With the Submission Date
Weple's app work asks about dates before screen counts in the first conversation. Whose name the developer account goes under, where the closed testing group comes from, whether managed publishing stays on: each of those is awkward to undo once building has started. So the review column and the account column go onto the calendar before the scope document gets written, and the screen list is built on top of them. What the work is counted in is set out on the pricing page. The order to follow when review comes back as a rejection is written up separately in The Rejection Email Already Says What to Fix. If the app is already in the console, the account type and the date of the last update are two lines enough for us to work out the wait still ahead of you.
In a similar spot
Send us where things stand and we reply with the scope and the price within 24 hours.