How to Publish an AI-Built (“Vibe-Coded”) App on Google Play
Built your app with an AI tool? What Google Play still needs: a real Android build, signing, accurate data declarations, security checks and testers.
Short answer
Google Play doesn’t care how the code was written, but it does care what the app does. You need a real Android App Bundle (native, Flutter, React Native or a TWA), a signing key you control, accurate Data safety and privacy declarations, no leaked API keys, and on a new personal account a 14-day closed test with 12 testers.
Step 1: Get a real Android build
AI app builders export in different ways:
| What you have | How to get an .aab |
|---|---|
| A Flutter project | Publish a Flutter app |
| An Expo / React Native project | Publish an Expo app |
| A Kotlin Android Studio project | Signed bundle in Android Studio |
| A web app only | Package it as a PWA with a Trusted Web Activity, or wrap with Capacitor |
If the tool built it for you, make sure you hold the upload keystore and know the package name.
Step 2: Security review AI code often misses
- API keys in the app. Anything shipped in an APK can be extracted. Move secret keys (OpenAI, Stripe secret, admin database keys) to a server.
- Open databases. Check Firebase or Supabase rules so users can’t read each other’s data.
- Unused permissions. Generated manifests often request more than needed. Remove extras.
Step 3: Declarations must match reality
AI-generated apps commonly include analytics, crash or ad SDKs the creator didn’t notice. Your Data safety form and privacy policy must reflect every SDK. If users can sign up, add account deletion.
Step 4: Minimum functionality
Thin apps (a single prompt box over an API, or a wrapped website) are at risk under Google Play’s quality and spam policies. Give it a clear purpose, a polished first run, offline handling and real value.
Step 5: Real testers
Testers will find the things AI didn’t test: odd devices, slow networks, permission denials. Recruit 15-20 through friends or a tester exchange, ship fixes during the 14 days, and describe them in your production access application.
AI-generated content in the app
If your app generates content with AI, read Google Play’s policies on AI-generated content (including user reporting of offensive output) in the Policy Center.
Frequently asked questions
Do I need to disclose that AI wrote my code?
Google Play doesn’t ask how your code was written. You must be accurate about what the app does, what data it handles, and any AI-generated content it shows users.
Can I publish an AI chatbot app?
Yes, if it follows Play policies, including those on AI-generated content and user reporting of offensive output. Keep API keys on a server.
What’s the biggest risk with AI-built apps?
Security mistakes: exposed secret keys and open databases. Review those before any tester installs the app.
Sources and how we keep this accurate
- Google Play Developer Policy Center
- Play Console Help: Provide information for Google Play’s Data safety section
- Play Console Help: App testing requirements for new personal developer accounts
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
10 Common Reasons Google Play Rejects Apps (and Fixes)
How to Fill Out the Google Play Data Safety Form
How to Publish a PWA on Google Play With a Trusted Web Activity
Closed Testing for Wear OS Apps: Finding Testers With Watches
Closed Testing for Android TV and Google TV Apps
How to Publish a FlutterFlow App on Google Play
Browse all guides, or see the quick answers, guides and comparisons.