How to Publish a Vibe Coded App in 2026: App Store and Google Play Checklist
A working vibe coding prototype is a start, but an app store needs a signed, installable build that survives testing on real devices. It also needs accurate privacy disclosures, a store listing, and enough information for reviewers to use the app. This guide walks a first-time indie developer through both stores in 2026 and shows where AI can save time without making unverified claims on your behalf.
First, check whether you have a website or an app
Do you have iOS and Android projects that you can build and sign, and versions you can install on physical phones? A website or PWA that runs in a browser does not automatically produce submissions for either store. A cross-platform framework can help, but you still need platform builds, permissions, signing, and store configuration.
| What you have | What to verify next |
|---|---|
| A website, PWA, or AI-generated frontend | Choose a maintainable mobile approach and identify the native capabilities and platform constraints you need. |
| iOS and Android projects | Install them on an iPhone and an Android phone; test launch, sign-in, key tasks, and permissions. |
| Installable builds | Check signing, version numbers, data flows, listing assets, and review forms against the actual app. |
Apple’s App Review Guideline 4.2 expects an app to offer enough functionality and value. A thin wrapper around a website may be rejected. Define the mobile product before choosing how to package it.
Prepare the accounts, builds, and disclosures
| Item | App Store | Google Play |
|---|---|---|
| Developer account | The Apple Developer Program is $99 per year. An individual account displays your legal name; organization enrollment involves a D-U-N-S Number. | Play Console has a one-time $25 registration fee and requires identity verification. |
| Build requirements | Upload a signed iOS build with Xcode. Since April 28, 2026, iOS apps submitted to App Store Connect must be built with Xcode 26 or later and the iOS 26 SDK. | New apps use an Android App Bundle (AAB) and Play App Signing. Since August 31, 2026, new apps and updates for phones and tablets must target Android 16 / API level 36 or higher; other device categories have exceptions. |
| Identity and assets | App name, bundle ID, version, icon, screenshots from the real app, description, and support URL. | Package name, version, icon, real screenshots, store description, and contact details. |
| Policy and review | Privacy policy, App Privacy answers, age rating, review credentials, and instructions. | Privacy policy, Data safety, content rating, target audience and ads declarations, plus any testing requirement for your account. |
Those are the fees shown on the official pages in US dollars; payment currency, taxes, and eligibility depend on your location and account. If you are publishing for a company, decide which legal entity should appear in the store before enrolling.
Inventory sign-in, notifications, camera, location, analytics, ads, payments, and third-party SDKs. Privacy forms describe what the app actually does with data, including third-party code. Google requires a Data safety form even when an app does not collect user data. If users can create accounts, Apple requires a way to initiate deletion in the app; Google requires an in-app path and a web link for deletion requests.
Three useful AI workflows before submission
1. Find release gaps. Give an AI assistant your project configuration, dependency list, platform build settings, and feature list. Ask for a table with evidence, missing items, and open questions. For example:
Based only on the project files I provide, audit our iOS and Google Play release readiness. Cover build formats, signing, versions, permissions, SDKs, listing assets, and test methods. Cite the file or evidence for every conclusion. Mark anything unsupported as “needs verification.” Do not ask for private keys, certificates, or passwords.
2. Draft a data-flow inventory. Supply the actual SDKs, API calls, permissions, retention rules, and third-party services. Ask AI to organize what is collected, why, who receives it, and how users can delete it. Then verify that draft against server logs, provider documentation, and real network behavior before completing App Privacy or Data safety. An AI-generated inventory is not evidence by itself.
3. Generate device tests and reviewer notes. Ask AI for cases covering first launch, registration, denied permissions, poor connectivity, purchases, sign-out, and account deletion based on features that exist. Turn confirmed test results into concise instructions for reviewers. Screenshots should show the real app; listing copy should describe features that are already working.
Test the candidate builds on real phones
Install each candidate on at least one physical iPhone and one physical Android phone. Record the device, OS version, app version, steps, and result. A successful build proves that a file was produced; it does not prove that a user can complete a task.
- Start from a fresh install and complete the primary task, including registration or sign-in if needed.
- Deny camera, location, or notification permissions and check that the app responds safely and explains why it asks.
- Test offline and slow connections, external links, backgrounding, and relaunch.
- If applicable, test purchase restoration, cancellation, sign-out, and account deletion.
- Run the full flow using the reviewer account. Apple’s Guideline 2.1 calls for valid demo credentials or a demo mode when review requires access.
For digital features or content sold in the app, read Apple’s Guideline 3.1.1 and the Google Play payments policy. Both have platform rules and regional exceptions. Do not select a checkout flow from a one-line AI suggestion.
iOS: from App Store Connect to review
- Enroll in the Apple Developer Program and complete the applicable identity, agreement, and payment setup.
- Create an app record in App Store Connect with the name, primary language, bundle ID, and SKU. Match the bundle ID in your project.
- Build, sign, and upload with an Xcode version that meets the current SDK requirement. Use TestFlight before release; the first build for external testers may require Beta App Review.
- Add the listing, real screenshots, support and privacy URLs, App Privacy answers, age rating, and any other applicable declarations. Give reviewers credentials and instructions for unusual flows.
- Select the build you tested and submit it for App Review. After approval, check its actual release status and store page.
If you distribute in the EU, also check the trader-status requirements in App Store Connect for your distribution and legal status.
Android: from Play Console to production
- Register for Play Console and complete identity verification. Some new personal accounts also need to verify a physical Android device through the Play Console mobile app.
- Create the app, confirm the package name, listing details, and contact information. Build a signed AAB, configure Play App Signing, and check the applicable target API requirement.
- Finish the store listing, real screenshots, privacy policy, Data safety, content rating, target audience, ads, and other App content declarations.
- Install and verify via an internal or closed testing track. For personal developer accounts created after November 13, 2023, production access requires at least 12 testers opted into a closed test continuously for 14 days, followed by an application for production access. Do not assume this applies to every older or organization account.
- Once your account meets its requirements, use the verified AAB to create a production release. After review, check the rollout countries, download, launch, and store information.
If the app itself generates AI content for users, review Google Play’s AI-generated content policy, including an in-app reporting mechanism where required. Using AI to help write code is a different situation from offering AI-generated content as an app feature.
Final pre-submission check
- Both platforms have candidate builds installed and tested through the core flow; the selected store builds match the tested versions.
- Screenshots, claims, permission prompts, and data disclosures match actual behavior. Privacy, support, and deletion links work.
- Reviewers can access sign-in-protected features. Payment, subscription, and account flows have been checked in their test environments.
- Account-specific identity and testing requirements are complete. Plan a fresh-install and listing check after release.
AI can speed up your checklist, test cases, and copy. The evidence that an app is ready remains an installable build, observed device results, and accurate disclosures. Official requirements in this article were checked on September 23, 2026; verify the linked Apple and Google pages and your console prompts again on submission day.
