How to publish a vibe-coded app to Google Play

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

Yes. Google Play takes Android apps uploaded as an Android App Bundle (an .aab file), not a link to your website, so a web app from Lovable, Bolt.new, Base44 or v0 needs a native Android build first.

You open Play Console expecting a publish button and find a checklist: identity verification, an Android device check, a two-week test with 12 people, then a set of forms. None of it is hard, but it catches people who planned to launch this weekend.

If your builder already makes native code (Rork, Emergent, Anything, Rocket.new, RapidNative or FlutterFlow), you can go straight to the account and the closed test. If it makes a web app, converting it to React Native and Expo gives you one app for Google Play and the App Store, on the same backend.

Should you open a personal or organization Google Play account?

Open an organization account if you have a registered business, because it skips the 12-tester closed test. Open a personal account if you don't, and plan for the test. Both cost a one-time US$25 fee.

• Google verifies your identity during setup and may ask for a government ID and a card in your legal name. The fee isn't refunded if those details turn out to be invalid.
• A D-U-N-S number is free from Dun & Bradstreet. Google warns that third-party services may charge high fees for it.
• Prepaid cards aren't accepted for the registration fee.

How does the Google Play 12 testers for 14 days rule work?

If your personal account was created after November 13, 2023, at least 12 testers must be opted in to a closed test when you apply for production, and they must have stayed opted in for the 14 days before that, without a break.

1. Create the app in Play Console and fill in the store listing basics.
2. Open Testing, then Closed testing, and create a track.
3. Upload your App Bundle to that track and roll out the release.
4. Add testers by email list or Google Group, choose your countries, and save. The opt-in link appears once the closed test release is published.
5. Send the opt-in link. Testers accept it with their Google account, then install the app from Google Play.
6. Keep at least 12 opted in for 14 days in a row. A tester who leaves and rejoins starts their 14 days again.
7. Apply for production from the Play Console dashboard. The form asks about your closed test, your app and its production readiness.

Invite 15 to 20 people, not 12, so one tester dropping out doesn't reset your plan. Google says the production application review usually takes seven days or less. More on finding testers in the 12-tester requirement and the closed test walkthrough.

What forms does Google Play Console ask for?

Before production, Play Console asks you to complete the App content declarations: a privacy policy, app access, ads, the content rating questionnaire, target audience and the Data safety form. Fill them in during the closed test so they don't hold up launch.

Google says every app published on Google Play needs the Data safety form, including apps on closed tracks and apps that collect no data. Answer for your third-party code too, not only your own.

If people can create an account, Google also asks for account deletion in two places: inside the app, and on a web page where people can request deletion without reinstalling. You enter that link in the Data safety form. How to add account deletion covers both stores.

What target API level and file format does Google Play require?

Since August 31, 2026, new apps and updates must target Android 16 (API level 36) or higher, and new apps have had to publish as an Android App Bundle since August 2021.

• Wear OS and Android Automotive OS apps need API level 35, and Android TV and Android XR apps need API level 34. Phone apps need 36.
• Existing apps must target API level 35 or higher to stay available to new users on newer Android versions.
• Google offered extensions to November 1, 2026 for apps that needed more time. That date has passed, so new submissions must meet the requirement.
• The requirement rises every year, so plan an update each summer to keep publishing.

If you build with React Native and Expo or Flutter, the target API level comes from the SDK version you build with, so updating the SDK is usually how you meet the new level.

How long does Google Play review take, and what gets apps rejected?

Google doesn't give one fixed review time for every app. It says some developer accounts get a more thorough review, which can take up to seven days or longer in exceptional cases, and that production access applications usually take seven days or less.

For a new personal account, count on about three weeks from the start of the closed test to production access: 14 days of testing, then the application review, then the review of your first production release.

• Fewer than 12 testers opted in, or testers who barely used the app. Google can ask you to keep testing.
• A Data safety form that doesn't match what the app and its SDKs collect.
• No account deletion web link when the app has sign-up.
• A build that targets an API level below the current requirement.
• No working test login in App access, so the reviewer can't see the app.

Can you publish to Google Play yourself?

Yes. The account, the closed test and the forms are all things you can do on your own, and the test itself is free. What it takes is a native Android build, 12 to 20 willing testers and two weeks of reminding them.

If your app is a web app, the native build is the hard part. We convert it to React Native and Expo and can run the closed test with vetted testers; see pricing and what it costs to publish a vibe-coded app. To compare every route, read the best ways to publish a vibe-coded app.