Skip to content
WebViewGold Vibe Coding to App Store
English
Get WebViewGold

Claude Code to Google Play

Seven days from Claude Code web app to Google Play, and what the closed test adds

On Android, the work itself fits into a week: the agent prepares the web app, you build the bundle and fill in the Play Console. Whether the app is public after that week depends on your developer account. New personal accounts must run a closed test first, and this plan treats that test as part of the schedule.

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

Three things that differ from the iOS plan

The package name is permanent

Google locks the package name with the first uploaded bundle. Choose it on day 1, not while the build is running; the naming guide explains what to pick.

A closed test may come first

A new personal developer account needs a closed test with at least 12 testers who stay opted in for 14 days in a row before production access can be requested.

More declarations up front

The Data safety form, the content rating and a web link for account deletion are filled in before review. They are forms, but they have to match what the code does.

The week, day by day

DayClaude CodeYou
1Reads the repository without editing and lists store blockersOpen the Play Console account, start identity verification, settle the package name
2Adds the privacy page, in-app account deletion and a public deletion pageReview the diffs, deploy, start recruiting testers
3Fixes the mobile layout and back-button dead ends, wires in one native featureTest every screen on a real Android phone
4Sets values in the WebViewGold configuration if you ask it toBuild the signed App Bundle in Android Studio or the Cloud Builder
5Writes and runs browser tests, drafts the Data safety answers from the codeUpload to internal testing and install from Google Play
6Drafts listing texts and instructions for testersComplete the listing, the content rating and app access with a demo login
7Fixes what your first testers reportRoll out to the closed track and send the opt-in link

The closed test, without wishful thinking

With an organization account or an older personal account, day 7 can end with a production submission. Google's review then usually takes a few days, sometimes up to a week for a new account. With a new personal account, day 7 ends on the closed track. The calendar is then: one week of work, 14 days of testing, a short application for production access, Google's answer, and only after that the production review.

There is no way around it, and testers who never open the app help nobody, because Google asks how you tested when you apply. What you control is the start date. Every day without a build on the closed track is added to the launch date, so upload the first acceptable build early and keep improving the web app during the test. Tester tips are in the guide to the 12-tester requirement.

Use the 14 days

  • Invite more than 12 people, because the count must not drop below 12 during the test.
  • Give testers concrete tasks: sign in, allow notifications, open the app once without a connection.
  • Ship web fixes immediately. They reach testers with the next app start and need no new bundle.
  • Collect native changes, such as a new permission, and upload them as one new build.
  • Keep notes on what testers reported and what you changed. You need them for the production access questions.

A prompt for the test phase

Prompt for Claude Code
We are starting a Google Play closed test for this web app, which runs inside a native Android WebView app.

1. Read the routes and features and write docs/closed-test.md: a short welcome text for testers, five tasks that cover sign-up, the main feature, notifications, offline behavior and account deletion, and the questions we want answered.
2. Create docs/test-feedback.md with a table: date, tester, device, what happened, type (web fix, native change, store listing), status.
3. When I paste tester feedback, add it to the table, propose the fix and tell me whether it needs a new app build or only a web deploy.

Do not change application code in this task.

Frequently asked questions

Does every Google Play developer account need the closed test?

No. It applies to new personal accounts. Organization accounts and older personal accounts can go to production directly.

Does the 14-day test delay my iOS release?

No. You can submit to Apple as soon as the iOS build is ready, then release iOS first or both apps together.

Do later updates need another closed test?

No. Once the app has production access, updates go to production without a new test. Most updates are web deploys anyway and need no store release at all.

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.

See plans on the main page

Cloud Builder

$349 per license, one-time add-on

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.

How the Cloud Builder works Try the free demo

Full Service

$698 per platform $798

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.

Full Service details Powered by WeSetupYourWebViewApp

Winter Sale prices valid until December 31, 2026.

Talk it through with our team

Free 15-minute call: your app, your tools, your next step

Rather start right away? See plans and pricing or hand it over with Full Service.