Ship to Google Play, including the 14-day testing gate nobody warns you about
Play is easier to publish to than the App Store and harder to plan around, because a new personal developer account has to run a closed test with a dozen real testers for fourteen continuous days before it can even apply for production.
- Typical timeline
- 4–7 weeks, driven by the testing window
- Pricing
- Fixed quote after a free readiness review
What this is actually about
The parts that decide whether the project takes three weeks or three months, and which nobody mentions until they bite.
- 01
The testing requirement is a calendar item, not a task
New personal developer accounts must run a closed test with a minimum number of testers opted in continuously for fourteen days before applying for production access.
- 02
Target API levels expire on a schedule
Play enforces a minimum target API level for new apps and for updates, and it advances every year.
- 03
The Data safety form is a legal declaration
It is a public statement about what your app collects, shares and encrypts.
- 04
Play is where the install cost is lowest
Android has the larger global install base, the store is more permissive about what qualifies as an app, and the $25 fee is one time rather than annual.
The sentences we hear most, and what we do about each one
Paraphrases of things founders have actually said on scoping calls. Left column is the experience; right column is the work.
"I finished the app and now I am told to wait two weeks"
The closed-testing requirement is the single most common launch-date surprise in Android right now.
How we helpWe start the closed track in week one, against an early build, and we help you assemble the tester list before there is anything to test.
"I do not have twelve people to test it"
This catches solo founders hardest. Testers must be real Google accounts that opt in and stay opted in, and recruiting a dozen of them is a genuine ask when the product has no users yet.
How we helpWe help you build the list from the people you already have - early access signups, a community you are in, colleagues, a small group we can help coordinate.
"My app was suspended and I do not know why"
Play enforcement is more automated than Apple's and the messages are less specific.
How we helpWe audit against the categories that actually trigger enforcement - permissions and their declared purposes, foreground service types, background location, financial and health categories, and the account deletion requirement - before submission.
"I lost my signing key"
An app signed with a key you no longer have cannot be updated.
How we helpPlay App Signing is enabled from the start, with the upload key held in your account and documented in the handover.
Everything that has to be true before you submit
We work through every one of these before the first submission, because finding them one rejection at a time is where the weeks go.
Account type decided first
Personal versus organisation changes the testing requirement and what shows publicly.
Closed testing track started early
The minimum tester count, opted in and continuous for fourteen days.
Android App Bundle, not an APK
Play requires the .aab format. Play App Signing on from the start so a lost upload key is recoverable.
Current target API level
Enforced for new apps and for updates, and it advances annually.
Data safety form matching the bundle
Filled in from a dependency audit, not from memory. It is a public declaration.
Account deletion, in-app and on the web
Play requires a deletion route inside the app and a publicly reachable web URL for people who have uninstalled it.
Permissions justified
Every sensitive permission needs a declared purpose. Foreground services need a declared type.
Store listing and privacy policy that resolve
Screenshots at the required densities, a feature graphic, and a privacy policy URL that returns 200 to a crawler.
Deliverables
Everything lands in accounts you own, with the certificates and keys in your name.
- Signed Android App Bundle with Play App Signing in your account
- Closed testing track set up and the fourteen-day clock started early
- Data safety form completed from a dependency audit
- Account deletion in-app and a public web deletion URL
- Permission and foreground-service declarations
- Complete store listing: screenshots, feature graphic, copy
- CI pipeline that builds and uploads a new version on a tagged release
- Handover: release runbook plus the target-API deadline in writing
Phases
Scope is fixed after phase one. Every phase ends in something you keep.
- 013–5 days
Readiness review and clock start
Free. We score the app against the policies that cause enforcement, settle the account type, and - critically - get an early build into a closed track so the fourteen-day requirement runs in parallel with the build rather than after it.
- 022–4 weeks
Build and instrument
The app is built against the current target API with the permissions it actually needs and nothing more.
- 031 week
Compliance and listing
Data safety form, account deletion routes, listing assets, content rating, and the declarations for whatever policy categories your product falls into.
- 041 week, plus 30 days support
Production and hand over
Apply for production access once the testing requirement is satisfied, roll out in stages, and watch release health.
What can go wrong, and what stops it
The testing window slipping the launch date
It starts in phase 1, before the app is finished. This is the whole reason phase 1 exists in this shape.
Testers opting out and resetting progress
We over-recruit against the minimum and check opt-in status through the window rather than at the end of it.
Suspension for an undeclared policy category
Categories are identified during the readiness review - financial, health, background location and foreground services are the usual ones - and declared before submission.
An upload key that cannot be recovered
Play App Signing from the first upload, with the upload key in your account and its location written into the handover.
Before you book the call
For a new personal developer account, yes. It is enforced by the console before you can apply for production access.
No. Bought or fabricated testers are a policy violation with account-level consequences, and the account is the thing you cannot easily replace.
Play, if you want to learn cheaply - one-time fee, more permissive review.
You have to update the app or you eventually cannot ship updates at all.
Related tracks
Apple App Store
Apple rejects wrapped web apps under guideline 4.2, and that is the single most common outcome for an app built in Base44, Replit or Lovable and dropped into a WebView.
Read the planReact Native rebuild
Lovable, Bolt, v0 and most Base44 front ends are React. That is the whole argument for React Native: the component model, the state handling, the validation rules and every line of your API layer come across largely intact.
Read the planWeb app → mobile
There are three ways to get an AI-built web app onto a phone, and they differ by an order of magnitude in cost.
Read the plan
Want a straight answer on the route?
The review is free and it ends in writing, including the case for the cheaper option.