Seven days from a Codex-built web app to Google Play, with the closed test planned in
On Google Play the work fits into a week, but the calendar may not. New personal developer accounts must run a closed test before production, so for them day seven ends with the test clock running. This plan is built around that fact instead of hiding it.
Free 15-minute call with our team, or call +49 761 519 751 50 (24/7, English + German)
Approval guarantee – or money back within 14 days
No coding needed
One-time payment, free updates
24/7 human support
Made in Germany since 2014 · ISO 27001
9:41
Your app
Your appNow live in your pocket
App Store · Google Play Approved
Three facts that set the pace
Your account type
A new personal developer account must complete a closed test with at least 12 testers for 14 days before it may publish to production. Organization accounts skip the test but go through their own verification. Check which one you have before you plan anything.
Package name and signing key
Both are fixed with the first upload. The package name can never change, and updates must be signed with the same key. Store the keystore where it cannot get lost.
Google's own review
After you submit, Google reviews the release. That usually takes a few days and can take longer for new accounts.
Seven days of work
Recruiting testers starts on day one, because it is the slowest step.
Day 1: create the app and invite testers
Create the app in the Play Console, settle the package name and send the first tester invitations today. In parallel, let Codex write a report-only audit of the repository: accounts, payments, permissions and every third-party service the code calls.
Day 2: Android-specific fixes in the web app
Tasks for Codex: account deletion inside the app plus a public web page for deletion requests, sensible behavior of the back button on every screen, and error states for failed requests.
Day 3: build and sign
Configure the WebViewGold Android project, generate the signed App Bundle, back up the keystore and upload to the internal testing track. If the build fails, the Gradle error guide helps.
Day 4: open the closed test
Move the build to a closed testing track, add the tester list and send the opt-in link. Under the testing rule, the 14 days only count while at least 12 testers are opted in.
Day 5: the console forms
Data safety, content rating, target audience, ads declaration, and app access with demo credentials. Answer from the audit of day one, not from memory.
Day 6: device tests
Two different Android phones if you can: sign-in, back button and gestures, no connection, file uploads, account deletion. Read the pre-launch report that the console creates for your build.
Day 7: listing, then submit or wait
Icon, feature graphic, screenshots from the real app, short and full description. Accounts without the testing rule submit for production today. Everyone else has finished the work and lets the clock run.
The closed test, treated honestly
For a new personal account, "Google Play in seven days" means ready in seven days, not live in seven days. Production access comes afterwards: 14 days of closed testing with at least 12 opted-in testers, then a request for production access that Google evaluates, then the normal review of the release. Invite more testers than you need, because the count can drop when people opt out.
The period is not lost time. Every deployment of the web app reaches the testers without a new upload, so their feedback can be fixed and checked within the same two weeks. The 12-tester guide has the details of the rule.
Where you stand after day seven
Account
End of day seven
What follows
New personal account
Closed test running, forms and listing complete
14 days of testing, production access request, review
Keep notes on who tested and what you changed. The production access request asks about your testing.
Frequently asked questions
Can I skip the closed test?
Not with a new personal developer account. Organization accounts are not subject to it, but they need their own verification, which also takes time.
What do testers have to do?
They opt in with their Google account through the link from the Play Console, install the app and stay opted in for the 14 days. Ask them to open the app several times.
Is the web app frozen during the test?
No. The app loads your live web app, so you can keep deploying improvements. Only native changes, such as a new permission, need a new upload.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.