25% of App Store submissions get rejected on the first pass. Google Play now requires 14 days of closed testing for new personal accounts. Android 16 (API 36) is mandatory from August 2026. Everything changed — here’s the current playbook.
Quick Summary: One: Apple rejects 25% of submissions on first pass — mostly for fixable reasons that could be caught in a pre-submission checklist. Two: New personal Google Play accounts must run 14 days of closed testing with 12+ testers before going live — if you don’t know this, you’ll lose 2–3 weeks at launch. Three: From August 31, 2026, all Android apps must target Android 16 (API level 36) — your developer must set this in the build config or your app gets blocked from new users on modern devices. This guide covers both stores in the order you’ll actually work through them: setup → assets → submission → launch. Working with us? Primocys handles submission for you →
This app store submission guide is written for founders, not developers. Whether you’re submitting to the App Store for the first time or managing an agency that will do it for you — knowing how the process works helps you plan your launch timeline, avoid the most common rejection reasons, and protect your launch date.
Submitting to the App Store and Google Play in 2026 requires more steps than it did two years ago. Apple’s privacy manifest requirement, Google Play’s mandatory Google Play closed testing period for personal accounts, and the Android 16 API 36 deadline have all added compliance steps that weren’t in older guides. This guide is current as of June 2026 — every step reflects what the stores actually require right now.
Primocys has submitted hundreds of apps to both stores for clients across the US, UK, UAE, and India. Every app store rejection reason in this guide is something we’ve seen in a real review email. Every checklist item is something that has caused a delay for a real client. Use this before you submit — not after you get rejected.
Step 1 — Set Up Developer Accounts Before Your App Is Ready
Both stores require developer account setup that takes time — and both have bureaucratic steps that can delay your launch if you leave them to the last week. Set up both accounts as soon as your app enters development, not when it’s finished.
Set up your Apple Developer account
- Enroll at developer.apple.com — Individual or Organisation account
- Individual: Apple ID + payment, approved in 24–48 hours
- Organisation: requires a D-U-N-S number (free from Dun & Bradstreet, 5–14 days if you don’t have one)
- Two-factor authentication is mandatory — set this up before anything else
- Add your developer team members in App Store Connect under Users and Access
- Set up banking and tax forms under Agreements, Tax & Banking — required before any paid apps or in-app purchases go live
Set up your Google Play account
- Go to play.google.com/console, sign in with Google, pay $25
- Identity verification required — government ID for personal accounts, business registration docs for organisation accounts
- Organisation accounts: have your D-U-N-S number ready, or wait weeks
- Account approval: 48 hours for personal, up to 2 weeks for organisation
- Personal accounts created after Nov 2023 must complete closed testing (12 testers, 14 days) before production access — organisation accounts skip directly to production
- Set up your payments profile under Monetise for in-app purchases
The Google Play testing requirement that surprises every founder launching for the first time: Personal Google Play Developer accounts created after November 2023 — which is essentially every new account — cannot submit to production until they’ve completed a closed testing period. You need at least 12 real testers who have opted into your test track, and the testing period must run for at least 14 continuous days. This is a minimum, not a target. Plan for this to take 3–4 weeks from the moment your app is ready, because recruiting real testers takes time.
Register as an organisation from the start if you can: — it bypasses this requirement entirely and saves you 3 weeks at the most stressful point in your launch.
Step 2 — App Store Submission Checklist (Prevent Rejections Before They Happen)
A rejection from Apple or Google doesn’t just delay your launch by a day or two — it triggers a full resubmission cycle that can take another 3–7 days. The checklist below addresses the most frequent rejection triggers before you hit submit.
- Privacy policy: Live URL, accessible without login, covers what data you collect and why
- Privacy manifest: Required NSPrivacyAccessedAPITypes entries for any APIs accessing camera, location, contacts, or health data
- Usage description strings: NSCameraUsageDescription, NSLocationWhenInUseUsageDescription — every sensitive API needs a human-readable explanation
- Demo/test account: If your app requires login, provide Apple reviewers with credentials in the App Review Notes
- All buttons functional: No placeholder text, no TODO buttons, no broken navigation — reviewers will test every visible UI element
- In-app purchases: All IAP products approved in App Store Connect before submission. Do not use external payment links
- App Tracking Transparency: Required ATT prompt before any advertising SDK calls if you use Facebook Ads, Google Ads SDK
- Support URL: Live page with contact information for users
- Privacy policy: Same as iOS — live URL required, must match your Data Safety declaration
- Data Safety section: Declare every data type your app collects, why, and whether it’s shared with third parties. Inconsistency between declared and actual behaviour = rejection or removal
- targetSdkVersion = 36: Android 16 is mandatory for all new apps from August 31, 2026. Set this in build.gradle before submission
- IARC content rating: Complete the free questionnaire (5 minutes) — mandatory for all apps to appear publicly
- App Bundle (AAB) not APK: Google Play now requires AAB format. Xcode/Android Studio generates this — confirm with your developer
- Permissions declared: Every permission in AndroidManifest must be present and justified. Undeclared permissions trigger automated flags
- Closed testing complete: 12 testers, 14 days minimum (personal accounts). Check status in Play Console before attempting production release
- Financial features policy: Apps handling finance, crypto, or loans need additional declarations and may require specific certifications by country
Step 3 — Store Assets That Convert Visitors Into Downloads
Your store listing is your app’s first impression for every user who finds it through search or browsing — and it directly affects your conversion rate from page visit to download. An app with a great icon and well-crafted screenshots converts 3–5× better than one with rushed assets, even if the underlying app is identical.
Screenshots — Your Most Important Store Asset
Screenshots are not documentation. They are marketing material. The best-performing screenshots show the core value proposition in the first image (before the fold in search results), use device mockups with actual UI rather than generic marketing illustrations, and have clear one-line explanations of each screen’s purpose overlaid as text.
- iPhone 15 Pro Max (required)1320×2868px
- iPhone 8 Plus (required)1242×2208px
- iPad Pro 12.9″ (required if iPad)2048×2732px
- Max screenshots per size10
- FormatPNG or JPEG
- Preview video (optional)15–30 seconds
- Phone screenshots (required)Min 320px, max 3840px
- Minimum screenshots2 (aim for 6–8)
- Feature graphic1024×500px JPEG/PNG
- App icon512×512px PNG (32-bit)
- FormatJPEG or 24-bit PNG
- Max file size per asset8MB
The ASO detail that improves organic discovery — App Store and Google Play both: Your app title and subtitle (App Store) or short description (Google Play) are the most heavily weighted fields for keyword ranking in both stores’ search algorithms. Front-load your primary keyword in the app name. Use the subtitle/short description to target your second-priority keyword. Both stores allow 30–80 characters in these fields — use every character intentionally. Your long description on Google Play is indexed for search (App Store’s is not) — write it with natural keyword density across the first 150 words where the algorithm weights heaviest. This is the free version of app store optimisation that every founder should do before spending anything on user acquisition.
Steps to Build a Mobile App from Scratch: The Complete 8-Step Process
Submitting to the Apple App Store — Exact Steps
1. Upload your build via Xcode or Transporter. In Xcode: Product → Archive → Distribute App → App Store Connect. This creates a signed IPA and uploads it to App Store Connect. Alternatively, use the Transporter app (macOS) to upload an IPA generated outside Xcode. The build appears in App Store Connect under TestFlight within 10–30 minutes of upload.
2. Create a new app version in App Store Connect. Under your app → App Store tab → click the + button next to versions. Add your version number (must match Info.plist CFBundleShortVersionString exactly), write your What’s New text (shown to existing users as an update), and link the build you uploaded.
3. Complete the App Privacy section. Declare every data type your app collects — location, usage data, identifiers, purchases. This feeds the Privacy Nutrition Label shown on the App Store listing page. Inconsistency between this declaration and your app’s actual behaviour is one of the fastest paths to rejection or removal post-launch.
4. Fill in App Review Information. This is where you add your demo account credentials, any special review instructions (how to access features that require special setup), and your contact phone number for Apple to call if they have a question. Many rejections happen because reviewers couldn’t access the core functionality — prevent this with clear instructions.
5. Submit for review. Click Submit for Review. Review typically begins within a few hours and completes in 24–72 hours. You’ll receive an email when the status changes. Check Resolution Center in App Store Connect if rejected — Apple’s messages are sometimes brief, but the specific guideline number tells you exactly where to look.
The one thing to do if Apple rejects your app: Don’t resubmit immediately with a partial fix. Read the rejection reason carefully, fix every issue it mentions, and do a fresh review of the full checklist before resubmitting. A second rejection triggers a slower review queue. If the rejection feels genuinely wrong, use the Reply to Reviewer option in Resolution Center — Apple reviewers do occasionally reconsider with a well-reasoned explanation. Never be defensive; be factual and specific.
Submitting to Google Play — Exact Steps
1. Complete closed testing (personal accounts only). Go to Testing → Closed Testing → Create Track. Add your testers’ email addresses or create an opt-in link. Testers must actively install and use the app. After 14 continuous days with 12+ testers, you’ll be eligible to apply for production access. Monitor the dashboard — Google shows your progress toward the requirement.
2. Upload your signed AAB. Go to Release → Production → Create New Release. Drag in your signed Android App Bundle (AAB) file. If your developer gave you an APK, ask them to regenerate as AAB — APK-only uploads are no longer accepted for new apps. Add release notes (what’s new) — these are shown to users during updates.
3. Complete the three mandatory compliance forms. These live under Policy → App Content in Play Console. Content Rating: complete the IARC questionnaire (~5 minutes, free, generates your rating automatically). Data Safety: declare every data type collected and whether it’s shared with third parties. Target Audience: confirm whether your app targets children (this triggers additional COPPA-related requirements if yes). All three must show a green checkmark before Google will let you submit.
4. Fill your store listing completely. App name (50 chars), short description (80 chars, appears in search results — your most important field), full description (4,000 chars, indexed by Google Play search), screenshots, feature graphic, app icon, and category. A listing with any blank required fields will be blocked from submission.
5. Submit and monitor. Click Submit and your app enters review. Most apps review in a few hours to 3 days. First-time submissions with sensitive permissions take up to 7 days. Google’s rejection messages are usually about specific policy violations — check the Policy Status section in Play Console for details.
App Store Rejection Reasons — What Actually Happens in 2026
These are the specific app store rejection reasons Primocys has seen in real App Store and Google Play review emails, ranked by how often they occur. Understanding these before submission is the difference between a 24-hour approval and a 2-week delay:
No privacy policy URL, or URL requires login to access, or policy doesn’t mention all data collected. Instant rejection every time.
Using Stripe, Razorpay, or any external payment for digital goods that should go through Apple’s IAP. Apple’s Guideline 3.1.1.
Using Apple APIs (camera, contacts, health, location) without corresponding NSPrivacyAccessedAPITypes entries in PrivacyInfo.xcprivacy.
App requires login and no test credentials provided. Apple reviewers cannot access the core features, so they reject for incomplete functionality.
App crashes on launch or during normal navigation. Apple tests on real devices, not just simulators. Crashes on older device models are common.
What you declared in Data Safety doesn’t match what your app actually does — e.g. declared “no location collected” but app requests location permission.
App does very little — a single web view, a simple calculator, or content that should be a website not an app. Apple rejects apps with minimal functionality.
From August 31, 2026, targetSdkVersion must be 36 (Android 16) or higher. Apps targeting lower API levels will be blocked from reaching new users.
How Long Does App Store Review Take? — Realistic 2026 Timeline
How long does App Store review take — and how does Google Play compare? Here’s the realistic phase-by-phase breakdown so you can plan your launch date without surprises:
| Phase | 🍎 App Store | 🤖 Google Play | Notes |
|---|---|---|---|
| Developer account setup | 1–2 days (individual) · 5–14 days (org, needs D-U-N-S) | 2 days (personal) · up to 2 weeks (org) | Do this during development — not at the end |
| Store asset preparation | 3–7 days | 3–7 days | Screenshots, icons, descriptions, feature graphic |
| TestFlight / Closed Testing | Optional but recommended (1–2 weeks) | Mandatory for personal accounts (14+ days) | The step that surprises most founders |
| Pre-submission compliance check | 1–2 days | 1–2 days | Run the checklist in this guide |
| App review | 24–72 hours (standard) | Hours – 3 days | First-time or sensitive apps: up to 7 days |
| Rejection + resubmit (if needed) | +3–7 days | +1–3 days | 25% of iOS first submissions get rejected |
| Total — best case | 5–10 days | 17–25 days (personal) · 3–7 days (org) | Never schedule marketing launch for submission day |
| Total — with one rejection | 10–18 days | 20–30 days | Build buffer into your launch plan |
“Schedule your marketing campaign, your press release, and your social media announcements for 7 business days after your App Store submission. Not the same day. Not the day after. Developers who publicly announce a launch date before App Store approval get burned every year — and 2026 is no different.”
We Handle Submission — Both Stores, Every Time, No Rejections
Every Primocys project includes full App Store and Google Play submission as standard — store listing creation, screenshot design, compliance forms, TestFlight/closed testing management, and resubmission if Apple or Google rejects for any reason. We’ve done this for 650+ apps. Rejections don’t delay your launch when we’re handling it.
Live on both stores now: Snaptaig, InstaClone, WasaaChat, ChatWave, Emoji Tale, Burpout — all submitted and approved by Primocys.
Submission included as standard
Store listing, screenshots, compliance forms, both stores. Not an add-on — it’s part of every build.
Rejection? We resubmit.
If Apple or Google rejects for any reason, we fix and resubmit at no extra cost. Your launch timeline is ours to protect.
Android 16 / API 36 compliant
All 2026 apps built with targetSdkVersion = 36. August deadline is already in our standard build config.
Privacy manifest built in
PrivacyInfo.xcprivacy configured correctly for every API your app uses. No last-minute compliance scrambles.
TestFlight / closed testing managed
We manage the 14-day Google Play testing cycle and TestFlight beta as part of the standard delivery process.
Flutter — both platforms at once
One Flutter build submits to both stores simultaneously. Clutch Top Flutter Developer 2024 & 2026.
Conclusion
Submitting your app to the App Store and Google Play in 2026 is manageable when you know what to expect. The three things that trip up most founders: Apple’s 25% first-pass rejection rate (mostly preventable), Google Play’s closed testing requirement for personal accounts (3–4 weeks if you don’t plan ahead), and the Android 16 API 36 deadline from August 31, 2026 (a hard requirement your developer must set).
Follow the app store submission checklist in this guide, buffer at least 7 business days between submission and your public launch announcement, and register as an organisation on Google Play if you can — it skips the 14-day testing wait entirely. If you’re working with Primocys, submission to both stores is handled as standard — including resubmission at no cost if Apple or Google rejects for any reason. Talk to us about your launch →
App Store & Google Play — Questions We Get Every Launch
How long does App Store review take in 2026?
Does Google Play require closed testing before launching in 2026?
What is the Android 16 API 36 requirement for Google Play in 2026?
Why do most App Store submissions get rejected?
Can Primocys handle App Store and Google Play submission for my app?
Related Articles
Build your scalable apps today.
Contact UsLeaving Already?
Hear from our clients and why 1200+ businesses trust Primocys
"Our B2B and B2C platform helps Nigerian manufacturers sell at wholesale prices and suppliers offer competitive retail pricing, with a strong focus on Made in Africa products and easy local and international distribution. The app has received excellent user reviews for its design and unique features. Communication with the Primocys team was smooth in an agile setup, even beyond office hours when needed. Their mobile app development expertise is excellent—highly professional and reliable."
"The dating app was delivered successfully and approved by both Apple App Store and Google Play. Our users are highly impressed with the design, UI, and overall functionality. The project was well planned with clear milestones, and all modules were delivered on time. The team is talented, patient, and flexible, accommodating multiple scope revisions as requirements evolved. Their 24/7 development and support availability made the entire process smooth and reliable."
" We hired Primocys to develop a highly complex and specialized mobile application, and they delivered outstanding results. The app includes advanced features such as timeline mixers, classifieds, payments, advertisements, GPS functionality, and more. Their technical skills, timely delivery, availability, and the personal attention Arpan Sagar brings to each project truly stand out. The team stays focused and committed from start to finish—an excellent experience overall."
" Great team with excellent communication and a strong commitment to on-time delivery. They developed a fully customized mobile app for both Android and iOS, perfectly matching our requirements. The entire process was smooth and professional, with clear updates at every stage. They are reliable, skilled, and very easy to work with. We’re continuing our partnership on more projects, and choosing them has been one of the best business decisions I’ve made."
AWARDS
Share Your Requirements
TRUSTED BY GLOBAL BRANDS
