Your app is built and tested. You expect to launch next week. Then Google Play asks for 12 testers over 14 days, and Apple rejects your first submission over a privacy detail you didn’t know existed.
Publishing is the step most founders underestimate. This guide from PWH Services explains how to publish an app on Google Play and the App Store in 2026: which accounts to open, what each store requires before launch, how long reviews take, and the most common reasons apps get rejected.
In this guide:
- The Short Answer
- Step 1: Choose the right developer accounts
- Step 2: Understand Google Play’s 12-tester rule
- Step 3: Prepare privacy and data requirements
- Step 4: Prepare your store listings
- Step 5: Submit and plan for review
- Common rejection reasons and how to avoid them
- A realistic launch timeline
- When to get help with publishing
- FAQs
The Short Answer
Here’s how to publish an app on both stores: you need an Apple Developer Program membership and a Google Play Console account, ideally registered to your business. You then complete each store’s privacy requirements, prepare listings, submit builds, and pass review.
Plan for at least three to four weeks for a first launch, not a few days. The biggest delays usually come from Google Play’s closed testing rule for new personal accounts (12 testers for 14 continuous days), business verification for organization accounts, missing privacy disclosures, and a first Apple rejection that needs a fix and resubmission.
Step 1: Choose the Right Developer Accounts
Both stores let you publish as an individual or as an organization. For a business, an organization account is almost always the better choice.
| Apple App Store | Google Play | |
|---|---|---|
| Account | Apple Developer Program | Google Play Console |
| Cost | Annual membership fee | One-time registration fee |
| Organization account needs | A registered legal entity and a D-U-N-S number | A registered business and a D-U-N-S number |
| Name shown on the store | Your company name (organization) or your personal name (individual) | Your developer name |
| Main advantage of organization accounts | Professional listing, easier team access | Exempt from the 12-tester closed testing rule |
Three things to get right from day one:
- Open the accounts in your company’s name, not your developer’s or agency’s. Moving an app between accounts later is slow and can cost you reviews and ratings.
- Start the D-U-N-S number early. Getting one can take several weeks, so request it while development is still in progress.
- Give your developers team access, not ownership. You stay in control if you ever change teams.
Step 2: Understand Google Play’s 12-Tester Rule
This is the rule that surprises most first-time founders.
If you publish with a personal Google Play account created after November 13, 2023, you can’t release your app to the public right away. According to Google’s own Play Console Help page, you must first run a closed test with at least 12 testers who stay opted in for the last 14 days continuously, then apply for production access.
What this means in practice:
- Budget at least two extra weeks, plus time for Google to review your production access request.
- Testers need to genuinely use the app. Simply installing it isn’t enough to pass.
- The requirement applies to each new app on a personal account.
- Organization accounts are not subject to this rule, which is one more reason to publish as a business.
If you’re already on a personal account, recruit testers from your network, early customers, or a waitlist, and give them a reason to use the app during those two weeks.
Step 3: Prepare Privacy and Data Requirements
Privacy is now one of the most common reasons apps are delayed or rejected. Prepare these before you submit:
| Requirement | Apple App Store | Google Play |
|---|---|---|
| Privacy policy URL | Required | Required |
| Data disclosure | App Privacy details (“nutrition labels”) | Data safety section |
| Account deletion | Required in the app if users can create an account | Required, including a way to request deletion |
| Third-party SDKs | Declare data collected by SDKs, privacy manifests where required | Declare data collected by SDKs |
| Data sent to third-party AI | Clear disclosure and explicit user permission first | Disclose in Data safety and policies |
If your app uses AI, read this carefully. Apple updated its App Review Guidelines in November 2025. Guideline 5.1.2(i) now says apps must clearly disclose where personal data is shared with third parties, including third-party AI, and get explicit permission before sharing it. In practice, a line in your privacy policy isn’t enough. If your app sends user messages, photos, voice, or documents to an AI provider, you need a clear in-app explanation and an opt-in before that data leaves the device.
Step 4: Prepare Your Store Listings
Your listing is what users see before they install. Each store needs:
- App name and short description that explain the value in plain language
- Full description focused on what the user gets, not technical features
- Screenshots for the required device sizes, and optionally a preview video
- App icon in the required sizes
- Category, keywords, and age rating questionnaire
- Support contact details and your privacy policy link
- A demo account for reviewers if your app requires login
Good listings also help people find you. Our app store optimization guide explains how to choose keywords and screenshots that improve visibility.
Launching soon and want it done right the first time? We prepare store accounts, privacy disclosures, listings, and submissions as part of our app development projects. Tell us where you are, and we’ll give you a fixed quote within 24 hours. Get a free launch review.
Step 5: Submit and Plan for Review
| Stage | Apple App Store | Google Play |
|---|---|---|
| Testing before launch | TestFlight for internal and external testers | Internal, closed, and open testing tracks |
| Review time | Often within a day or two, sometimes longer | Can take up to several days, longer for new accounts |
| Common first outcome | A rejection with requested changes is normal | Requests for policy or data safety fixes are common |
| Release options | Manual release, automatic, or phased release | Staged rollout to a percentage of users |
Tips for a smoother review:
- Submit to both stores as early as possible, then fix issues in parallel.
- Use a phased or staged release so problems affect fewer users.
- Reply to reviewer messages quickly and clearly. Most rejections are resolved with one or two rounds of changes.
Common Rejection Reasons and How to Avoid Them
| Rejection reason | How to avoid it |
|---|---|
| App feels incomplete, with placeholder text or broken links | Remove every unfinished screen and test the full journey |
| Thin app that is mainly a website inside a shell | Add genuine app value: native navigation, notifications, offline use, device features |
| Missing or inaccurate privacy details | Match your disclosures to exactly what the app and its SDKs collect |
| No account deletion option | Add in-app account deletion if users can sign up |
| Reviewer couldn’t log in | Provide a working demo account and clear notes |
| Crashes on review devices | Test on real devices and older operating system versions |
| AI data sharing without consent | Show a clear disclosure and get opt-in before sending data to an AI provider |
| Misleading screenshots or metadata | Show only features that exist in the submitted build |
If your app was built with an AI tool or a no-code platform, our guide on how to get a vibe coded app on the App Store covers the extra issues those apps often face.
A Realistic Launch Timeline
| Task | Typical time |
|---|---|
| D-U-N-S number and organization account setup | 1 to 4 weeks, start early |
| Privacy policy, disclosures, and listings | 3 to 7 days |
| Closed testing for a new personal Google Play account | 14 days minimum, plus production access review |
| First App Store review | A few days, including one possible resubmission |
| Fixes after first feedback | 2 to 7 days |
A first launch usually takes three to four weeks from “the app is ready” to “the app is live” on both stores. A second app from the same organization account goes much faster.
When to Get Help With Publishing
Here is the honest part. Once you know how to publish an app, many founders do it successfully on their own, especially with a simple app and an organization account already in place.
Consider getting help if:
- Your launch date is fixed, such as a marketing campaign or investor demo.
- Your app uses AI, health data, payments, or children’s content, where review is stricter.
- You’ve already been rejected and aren’t sure what the reviewer wants.
- Your app was built with an AI tool and you’re not sure it’s ready for review.
Before you submit, make sure the app itself is ready: see AI-Generated Mobile App to Production.
If your app isn’t built yet, start with our guide for founders who think I have an app idea, where do I start? If you built it with Lovable and got stuck, see how to hire a Lovable developer.
Ready to Publish Your App Without the Surprises?
At PWH Services, we build mobile apps for iOS and Android and take them all the way to launch: developer accounts, privacy disclosures, store listings, testing, and submission. We’ll review where you are, give you an itemized fixed quote within 24 hours, and tie payments to milestones you approve. Every account stays in your company’s name.
- See our mobile app development services
- Request a fixed quote
- Book a 30-minute call
- Agency or consultant? Join our partner program.
Frequently asked questions
Written by the PWH Services team, who design and build mobile apps, websites and AI products for startups and growing businesses.
