How to Publish Your Vibe-Coded Android App on Google Play

AI tools changed how fast you can build Android apps. What used to take months of learning Java and Android Studio can now take days — describe what you want, iterate with Cursor or Claude, and you have a working APK. The building part got easy. The publishing part didn't.

Google Play has requirements that have nothing to do with your code quality or how you built the app. The process catches most first-time publishers off guard, especially those who built fast and expected to ship fast. This guide walks through every step — including the one that trips up almost everyone.

Does Google care that you used AI to build your app?

No. Google Play review focuses on what your app does, not how the code was written. AI-generated code, low-code platforms, and manual coding are all treated the same. What gets apps rejected is policy violations — spam, misleading content, dangerous permissions, malware — not development methodology.

Build fast, build with whatever tools work for you. The publishing requirements are the same for everyone.

The full path from APK to live listing

Here's the complete sequence. Nothing can be skipped.

Step 1: Set up your developer account

Go to play.google.com/console and register as a developer. The one-time fee is $25. You'll need to verify your identity — Google now requires identity verification for all new personal developer accounts, which can take 1–3 days.

Use your real information. Mismatches between your payment method, identity documents, and account details cause delays.

Step 2: Prepare your APK or AAB

Google Play requires an Android App Bundle (.aab) for new apps, not a plain APK. If you built your app with Android Studio, you can generate an AAB from Build → Generate Signed Bundle. If you used a cross-platform tool like Flutter, React Native, or a no-code platform, check its documentation for how to export a signed AAB.

Your app must be signed with a keystore. Keep your keystore file and password somewhere safe — you cannot update your app without it.

Step 3: Create your app listing

Before you can upload anything, Google requires your store listing: app name, short description, full description, screenshots (at least 2), and a feature graphic. You also need to complete the content rating questionnaire, declare your app's target audience, and fill out the data safety section.

The data safety section is often overlooked and can cause delays if incomplete. Declare every type of data your app collects, even if it's just crash reports.

Step 4: Start closed testing — the wall most developers hit

Here's what almost nobody tells you when you're excited to ship your first app: before you can make your app public, Google requires you to run a closed testing period with at least 12 active testers for 14 consecutive days. This applies to all personal developer accounts.

To set up closed testing:

1. In Play Console, go to Testing → Closed testing → Create track
2. Create a Google Group (groups.google.com) for your testers
3. Add that Google Group to your closed testing track in Play Console
4. Upload your AAB to the closed testing track
5. Share the opt-in link with your testers — this is Play Console → Closed testing → Copy link

Each tester must: join your Google Group, click the opt-in link on an Android device, and install the app from the Play Store. All three steps are required. A tester who joins the group but never installs the app does not count as active.

Step 5: Find your 12 testers

This is the actual challenge. Most vibe coders hit the closed testing requirement and immediately think "I'll just ask friends" or "I'll post on Reddit." Both approaches have high dropout rates — testers say yes and then never complete the three-step opt-in process.

The most reliable free approach is a mutual testing exchange. AppSwap is built exactly for this situation: you test someone else's Android app, earn a credit, and that credit attracts a real developer-tester to your app. Because every tester on the platform is also a developer who needs testers, they have a direct incentive to complete all three steps.

Other options that work: Telegram developer communities (real-time, personal), Discord servers with beta test channels, and targeted outreach in communities where your app's target users gather.

Recruit at least 15 testers, not 12 — you need buffer for dropouts. If 3 testers go inactive during the 14-day period and your active count drops below 12, the counter resets to zero.

Step 6: Wait out the 14 days

Once 12 testers are simultaneously active, Google starts counting. The counter runs in the background — check your progress in Play Console under Testing → Closed testing → View release details.

During this period: keep your app stable (don't push breaking updates), make sure your store listing is fully complete, and respond to any tester feedback. Crashes during closed testing can affect your production access review.

Step 7: Apply for production access

After 14 days with 12+ active testers, Play Console will show that you're eligible to apply for production access. Go to Publishing overview → Request access to production.

Google reviews production access applications manually. For new personal developer accounts, this typically takes 1–3 days. You'll get an email when it's approved. Once approved, you can publish your app to all users.

Mistakes vibe coders specifically make

Waiting until the app is "finished" to start the process. The closed testing period takes at minimum 14 days after you have 12 testers. You can run closed testing on a working beta — it doesn't need to be the final version. Start the process as early as you have something that runs without crashing.

Using personal Gmail accounts instead of a Google Group. The closed testing track requires a Google Group, not individual email addresses. A group at groups.google.com is free to create and takes two minutes to set up.

Treating the 12-tester count as a checkbox. Google requires 12 active simultaneously for the entire 14-day period. If your count drops below 12 because testers leave the group or uninstall the app, the counter resets. Watch the number daily and add new testers if it drops.

Shipping an unstable version to closed testing. You built fast, but the closed testing version needs to be stable enough to run on diverse Android devices without crashing. A test track full of crashes can complicate your production access review.

Ignoring the data safety section. This is a frequent cause of app rejection in production access review. Fill it out completely and honestly — declare every type of data your app collects, processes, or shares.

Realistic timeline

From "my app is done" to "my app is live on Google Play":

• Days 1–2: Set up developer account, complete identity verification
• Days 2–4: Prepare AAB, complete store listing and data safety form
• Days 3–7: Recruit 12–15 testers (2–5 days with AppSwap)
• Days 7–21: Closed testing period (14 days once all testers are active)
• Days 21–24: Production access review (1–3 days)
• Day 24+: App goes live

Three to four weeks is the realistic minimum. Plan accordingly — don't promise a launch date before you've started the process.

Frequently asked questions

Related articles