Mobile 11 November 2026 6 min read

The Play Store review process, honestly

Teams budget for the build and forget the release. What actually holds an Android app at the door — background-location justification, data safety declarations, reviewer access, and a target-SDK deadline nobody put in the calendar.

Every mobile plan we have ever seen budgets for the build. Almost none of them budget for the release. The app is finished, somebody uploads it, and a week disappears into a queue of forms nobody costed — work that is not difficult, only invisible until you are standing in front of it with a launch date already announced.

The video you did not know you had to make

If your app requests location in the background — and whether it should is a design question before it is a technical one — Google requires a written justification and a screen recording that demonstrates the feature.

The recording is a genuine deliverable, not a formality. It has to show the in-app flow that leads to the permission, the disclosure screen where you explain in your own words why the app needs background location, the system dialog itself, and then the feature working with the data it collected. Narrated or captioned, so someone can follow it without knowing your product.

The part that catches teams is the disclosure. You cannot rely on the operating system’s dialog to explain yourself. There must be a screen of yours, before the system prompt, that states plainly what is collected, when, and why. If your app goes straight to the OS dialog because that was the fastest path in development, the video will show that, and it will be refused.

This is the requirement that blocked a release for us. Our video demonstrated the tracking working perfectly and never showed the disclosure screen, because the tester had already granted permission on that device. The fix was a fresh install and a re-record. The delay was days, because every resubmission rejoins the queue at the back.

Data safety, and three things that have to agree

The data safety declaration asks what you collect, why, whether it is shared with anyone, whether it travels encrypted, and whether a user can request deletion.

The trap is that three sources of truth must agree: what the app actually does, what the declaration says, and what your privacy policy states at the URL you supplied. Reviewers compare them. A declaration that omits a category the app plainly collects, or a privacy policy written for a different product and never updated, is a straightforward rejection.

Fill it in with someone who knows what the code sends. Analytics libraries, crash reporters and push services all collect on your behalf, and they belong in the declaration whether or not you think of that data as yours. The same blind spot shows up under HIPAA, where error monitoring is the third-party service teams forget.

Reviewers cannot sign up

If your app is behind a login, a human being has to get in to review it. That means credentials in the app access section, and they have to keep working.

The failure modes are all the same shape. A test account that expired. An account tied to an email one-time code sent to an inbox nobody monitors. A role-gated app where the supplied account has the wrong role and sees an empty screen.

Create a permanent reviewer account, give it realistic data so the app looks like a working product rather than an empty shell, and test it from a device that has never seen your app. If you use one-time codes, provide a route that works for someone outside your organisation.

The deadline that is not technical

Google raises the target API level that apps must meet, on a schedule. Once the deadline passes you cannot publish updates to an app targeting an older level, and eventually it stops being offered to new users on current devices.

This is a calendar item disguised as an engineering task. Nothing breaks on the day; your app keeps working for everyone who has it. You discover the problem at the worst possible moment, when you need to ship an urgent fix and the upload is refused.

Put the date in the same place you keep domain renewals and certificate expiries, and treat the upgrade as scheduled maintenance rather than an emergency.

The other queue-shaped surprises

A new personal developer account cannot go straight to production: Google requires a period of closed testing with a minimum number of real testers first, and the clock only starts once you have enough of them. Certain permissions carry declarations of their own, too — all-package visibility, SMS and call log access, accessibility services. Each is another form, and another possible round trip.

How to plan around all of it

Submit early, before you need to. Push a build to a closed track weeks ahead of launch with the declarations complete, and let the first review happen while you still have time to answer it. The purpose is not to ship; it is to find out what they will ask.

Treat the store listing as part of the build: the screenshots, the privacy policy, the data safety form, the reviewer account and the justification video are deliverables with owners and dates, in the plan beside the features.

Then assume at least one round trip. Reviews are conducted by people applying policies to an app they have never seen, and the first answer is often a question. Budget for the second submission and you will rarely need to explain a slipped launch date.


We take Android and iOS apps through store review, declarations and all. Tell us what you are trying to ship.

Building something like this?

Tell us what you're trying to do and we'll tell you honestly what it involves.

Start a conversation