Skip to content
Winter Sale from $619, until 31st December 2026 Book now
From agentic coding tool to Google Play Android · Google Play

Vibe-Coded App to Google Play: From Developer Account to Production Access

Google Play publishes AI-built apps like any other – after a sequence of gates: a verified developer account, a signed App Bundle targeting API level 36, the App content forms and, for new personal accounts, a 14-day closed test with at least 12 testers before you may even apply for production. Plan the calendar first, then fix the app-level problems vibe-coded projects usually bring along.

6 min read

Key takeaways

  • The account type decides the timeline: new personal accounts must pass a closed test with 12 testers over 14 days, organization accounts do not.
  • Choose the package name and keep the upload key safe from day one – both outlive every tool you used to build the app.
  • Most vibe-coded Android apps fail on behaviour, not code style: a back button that exits, dead upload fields, broken sign-in, someone else's website in a frame.
  • A coding agent can fix the app and keep it on the current target API level; Play Console declarations stay your responsibility.

Gate 1: The developer account

Everything on Google Play starts with a Play Console developer account, and the type you choose shapes the next weeks:

Personal accountOrganization account
WhoAn individualA company or other legal entity
IdentityPersonal identity checks; new accounts verify a physical Android deviceOrganization details and a D-U-N-S number
Before productionIf created after November 13, 2023: closed test with at least 12 testers, opted in for 14 consecutive daysNo mandatory closed test
Shown on the storeYour developer name and contact detailsThe organization

If you build the app for a business, register the business. It is the honest choice for users, and it removes the mandatory test period – though a real test is still a good idea.

Gate 2: A build Google Play accepts

Play only takes what it can verify and serve. Whatever your tool generated, the upload has to meet these rules:

  • Android App Bundle. New apps upload AAB files, not APKs. Expo projects get one from EAS Build; native projects from Gradle's bundleRelease; web apps need a wrapper or a Trusted Web Activity first.
  • Play App Signing and your upload key. Google keeps the app signing key; you keep the upload key. Store it in a password manager with a backup. If it is lost, an upload key reset through Play Console is possible but takes time.
  • A permanent package name. Pick com.yourcompany.yourapp deliberately. Builders sometimes generate one for you that you cannot change later.
  • Target API level 36. Required for new apps and updates since August 31, 2026. Older templates still target lower levels – see the target API guide.
  • A new version code per upload. Play rejects a version code it has already seen.

Tool-specific details are in our guides for Bolt Expo apps, Replit Agent apps and Lovable apps.

Talk to an AI Code Engineer about shipping your app to Google Play.

In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.

Gate 3: The App content forms

Play Console's App content section collects declarations about your app. None of them can be generated by your AI tool, because each one is a statement you are accountable for:

  • Privacy policy – a public URL that matches what the app does.
  • App access – working credentials so reviewers can get past the login.
  • Ads – whether the app shows ads.
  • Content rating – a questionnaire that produces the age ratings.
  • Target audience – if children are part of it, stricter rules apply.
  • Data safety – what the app and its SDKs collect and share, including data sent to AI providers. Our Data safety playbook shows how an agent can prepare the inventory.
  • Account deletion – for apps with accounts, a deletion option in the app and a web link where users can request deletion.

Gate 4: The closed test

For new personal accounts this is the longest gate. At least 12 testers must be opted in to a closed test for 14 consecutive days; internal testing does not count. Afterwards, the production access application asks how the test went – what testers found and what you changed.

Three things make it go smoothly:

  1. Recruit more than 12 people. Someone always drops out, and the 14 days count only while at least 12 stay opted in.
  2. Give testers concrete tasks and one place to report problems.
  3. Ship updates during the test. Fixed bugs and new builds are the clearest evidence that you tested seriously.

Our guide to the 12 testers and 14 days rule covers the details and the common reasons applications are turned down.

What vibe-coded Android apps typically get wrong

SymptomWhy it happensWhat fixes it
The back gesture closes the appThe WebView or navigation stack ignores back eventsBack steps through history; leave only from the start screen
Upload fields do nothingA WebView needs a file chooser implementationImplement it and test camera and gallery uploads
Google sign-in shows an errorGoogle blocks OAuth inside embedded WebViewsCustom Tabs or native sign-in
Blank screen for some usersPlain http:// calls are blocked by default on modern AndroidHTTPS everywhere
Rejection for spam or impersonationThe app frames a website you do not ownOnly your own content; see the Webviews policy guide
Rejection for broken functionalityThe builder's backend paused or a credit limit ran out during reviewKeep the backend running and monitored – see the broken functionality guide
Payment policy issuesStripe checkout for premium featuresGoogle Play Billing for digital goods

A coding agent fixes most of these quickly once you name them. Give it one symptom per task, ask it to reproduce the problem first, and test the fix on a real device.

Gate 5: Production, and staying there

Once production access is granted, release with a staged rollout and watch crashes and ANRs in Android vitals. Read the pre-launch report for every upload – Google runs the build on real devices before your users do.

Staying on Google Play means keeping up: the target API level rises every year, libraries such as Play Billing are deprecated on a schedule, and every new SDK changes your Data safety answers. These are well-defined tasks for an agent. Our playbook on maintaining AI-built apps after launch describes the routine.

If you would rather not run the gates yourself, our AI Code Engineers handle signing, CI/CD, the closed test set-up, the forms and the release in your own account – see the Android submission service. For the iPhone version, read vibe-coded app to the App Store.

Checklist: vibe-coded app on Google Play

  • Developer account type chosen; identity and device verification complete.
  • Package name final; upload key backed up outside the project.
  • Signed App Bundle targets API level 36 with a fresh version code.
  • Privacy policy, App access, ads, content rating, target audience and Data safety forms complete.
  • In-app account deletion plus a web deletion link for apps with accounts.
  • Back navigation, uploads, sign-in and HTTPS tested on a real device.
  • Closed test with at least 12 opted-in testers ran for 14 days, with updates shipped during the test.
  • Pre-launch report reviewed; release planned as a staged rollout.

Frequently asked questions

Can I publish an app built with an AI tool on Google Play?

Yes. Google Play reviews the app and your declarations, not the tool that wrote the code. The same account, testing, policy and technical requirements apply as for any other app.

Do I have to do the closed test?

If you have a personal developer account created after November 13, 2023, yes – at least 12 testers opted in for 14 consecutive days before you can apply for production access. Organization accounts are not bound by this rule.

My builder exported an APK. Can I upload that?

New apps on Google Play must be uploaded as Android App Bundles. Build an AAB from the project – with Gradle, EAS Build or your wrapper tool – and sign it with your upload key.

Can you take our app through Google Play for us?

Yes. Book a free call and an AI Code Engineer looks at your app and your Play Console status with you. We can take over signing, testing tracks, policy forms and the release in your own account.

Free, 15 minutes, no obligation

Get your app from agent output to approved release.

Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.

AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.

Ready to ship?

Talk to an AI Code Engineer – free, 15 minutes, in English or German.

Book a call for free

Chat and hotline are open 24/7. Answers from our senior AI Code Engineers (real humans) usually take closer to 72 hours than 1 hour.