How do I get my vibe-coded app on Google Play?

You just built an app in an afternoon – Lovable spat out a working web app, or Base44 wired up the whole thing while you drank your coffee, and it actually does the job. Now you want it on Android, sitting in the Google Play Store, tappable from a real phone with your icon on the home screen, so you ask ‘how do I get my vibe-coded app on Google Play?’

And that is where a lot of people get stuck!

Because building the app was the easy bit. Getting an AI-built app through Google Play in 2026 is a different sport, with its own rules, its own waiting rooms, and one requirement that catches almost everyone out. So let me walk you through what actually happens, what trips people up, and how we get a vibe-coded app onto Play without the drama.

Can you even publish a vibe-coded app to Google Play?

Yes. But not in the form it comes out of the builder.

Lovable, Base44, Bolt and the rest give you a web app. It runs in a browser. Google Play does not accept a URL: it accepts an Android app package (an AAB file, the Android App Bundle). So before Play will look at your app, it has to be a real Android build with a proper package name, signing keys, permissions, an icon, a splash screen and all the native plumbing underneath.

That is the wrapping step. We take your vibe-coded app and wrap it so it behaves like a native Android app: back button works, deep links resolve, push notifications fire through Firebase Cloud Messaging, and the thing launches from the app drawer like anything else on the phone. No browser bar. No “add to home screen” nag. A proper app.

You can technically do this yourself with Capacitor or Trusted Web Activities. Plenty of people try. The gap between “it runs on my machine” and “Google approved it for production” is where the weeks go.

“The build isn’t the hard part any more. The AI does that in minutes. It’s everything Google demands after the build that eats people alive. That’s the part we take off their plate, so they never have to learn what an AAB signing key is.” Ian Naylor, Founder AppBuild.diy

What’s the 12 testers, 14 days rule and why does it matter?

Here is the one that surprises everyone:

If you registered a personal Google Play developer account after 13 November 2023, Google will not let you publish to production until you have run a closed test with at least 12 testers, opted in continuously for 14 days (Google Play Console Help). Not 12 downloads. Not 12 clicks. Twelve real people, opted in, staying opted in, for two full weeks.

It used to be 20 testers. Google dropped it to 12 in December 2024, but the 14-day clock has never budged. And if a tester opts out halfway through, their days reset. If you are one tester short on day 13, you wait.

So the honest version of “how long until my app is live on Android” is: build time, plus wrapping, plus 14 days minimum of closed testing, plus review. People plan a launch for next Tuesday and then discover they needed to start recruiting testers a fortnight ago.

Organisation accounts registered as a real business are exempt from the tester rule entirely, which matters if you are doing this at any scale. That is one of the first things worth sorting before you build, not after.

Why not just leave it as a web app or a PWA?

Because Android users expect an app in the store, and the store is where they look.

A Progressive Web App can live on the home screen, sure. But it does not show up when someone searches Google Play, it has weaker access to native features, and on Android a chunk of your audience will simply trust a Play listing more than a link you paste into WhatsApp. There are more than 1.9 million apps on the Play Store depending on which count you believe (Business of Apps), and being in that catalogue is still how a lot of people decide you are real.

A native wrap also unlocks the stuff a raw web build cannot do well: reliable background push, biometric login, better offline behaviour, and the performance that stops your app feeling like a website in a costume.

“I always ask people the same thing: Do you want a link, or do you want an app? Because your customer already knows the difference, even if they can’t explain it. They can feel when something’s a webpage pretending.” David Hall, CEO Appbuild.diy

What usually breaks when an AI-built app goes to Google Play?

A few things, and they are predictable, which is good news because predictable means fixable.

First, permissions. Vibe-coding tools love to request things “just in case.” Google now asks you to justify sensitive permissions, and an app asking for location or contacts with no clear reason gets bounced. We strip the ones you do not need.

Second, the data safety form. Every Play listing needs an honest declaration of what data the app collects and where it goes. AI builders often bolt on analytics or third-party SDKs you did not consciously choose, and if your form does not match what the app actually does, that is a rejection.

Third, broken states. The classic vibe-coding bug: it works on the happy path and falls over the moment someone loses signal, rotates the screen, or taps back twice. We test the app on real Android devices and fix the niggles before it goes anywhere near a reviewer.

Fourth, target API level. Google requires apps to target a recent Android version, and a wrapped build has to meet that bar or it will not even upload. Small thing, hard stop.

How long does the whole thing actually take?

Ballpark, and being honest about it: the wrapping and fixing is fast, usually days. The 14-day closed test is the fixed cost you cannot compress. Google review after that is typically a few days, sometimes hours.

So from “my Lovable app works” to “it’s live on Google Play” you are realistically looking at two to three weeks if you start the testing clock early, and longer if you find out about the tester rule on launch day. The trick is to run the closed test in parallel while we sort the wrapping, so the 14 days are ticking in the background rather than tacked on at the end.

The vibe-coding wave is only making this more common. Around 63% of people using vibe-coding and AI app builders have no coding background (Hostinger), which means a lot of genuinely good apps are being built by people who have never seen a Play Console dashboard and have no reason to know what an AAB is. That is fine. That is what we are here for.

“Getting rejected by Google isn’t a verdict on your app. Half the time it’s a checkbox on a form or a permission you didn’t know you asked for. Boring reasons. We just know where the boring reasons hide, so you don’t lose a launch to one.” David Hall, CEO Appbuild.diy

Apple too, or just Android?

Both, usually – Most people who wrap for Google Play want the same app on the Apple App Store, and it makes sense to do them together because the wrapped codebase serves both. Apple has its own gauntlet (Guideline 4.2 and the “is this just a website” test), which is a whole separate conversation, but the point is you build once and we ship to both stores.

If you want the app on Android first because that is where your audience is, we can absolutely start there.

FAQ

Do I need a Google Play developer account? Yes, and it costs a one-off 25 dollars. Register as an organisation if you can, because personal accounts trigger the 12 testers, 14 days requirement and business accounts do not.

Can you use my existing testers, or do you find them? Either. If you have 12 willing people, great, we get them opted in properly. If you do not, we help you sort the closed test so the clock starts as early as possible.

Will wrapping change how my app looks? No. Your Lovable or Base44 design stays exactly as you built it. Wrapping adds the native shell around it, it does not touch your screens.

What if my vibe-coded app has bugs? We fix them first. Wrapping a broken app just gives you a broken app in a nicer box, so the niggles get sorted before the build goes to Google.

Is a wrapped app allowed on Google Play, or will it get flagged as a web wrapper? Allowed, when it is done properly. Google rejects lazy wrappers that are just a browser pointed at a website. A real wrap with native features, offline handling and proper integration passes fine, and that is the difference we build in.

How much does it cost? Far less than a bespoke Android build from an agency, which runs into the thousands per platform. You keep the app you already made and we handle the native side.

Building the app was the fun part, and vibe-coding tools deserve the hype for that. Getting it live, tested, approved and actually on people’s phones is the part that turns a weekend project into something real. If you have got a Lovable or Base44 app sitting there working, and you want it on Google Play without learning what an AAB signing key is, come and see us at appbuild.diy.

We will get it wrapped, fixed and shipped.

David, CEO AppBuild.diy

Last Updated on September 18, 2026 by Becky Halls