App Store and Google Play Submission Requirements: A 2026 Launch Checklist

Blog Summary: Most app launches that slip don't fail on code. They stall at submission. This guide covers the current Google Play submission requirements and App Store submission requirements as of October 2026, how to publish on both stores, the most common rejection reasons, and an app launch checklist to use before every release.

Introduction

Store rules change every year, and the cost of missing one is a delayed launch. On Android, the Google Play submission requirements now include targeting Android 16 for new apps and updates, and new personal developer accounts must run a two-week closed test before they can publish at all. On iOS, Apple says its App Review team reviews 90% of submissions in under 48 hours, but more than 40% of unresolved issues relate to a single guideline: 2.1, App Completeness.

Many launch guides still list older rules, such as earlier Android API levels or a 20-tester requirement that Google has since reduced to 12. This guide uses Apple's and Google's official documentation to explain the Google Play submission requirements and App Store submission requirements that apply as of October 2026.

What Are Google Play Submission Requirements?

Google Play submission requirements are the technical, privacy, and policy rules an Android app must meet before Google will publish it. They cover your developer account, testing, the app's target API level and file format, privacy disclosures, and the store listing. Apple has its own App Store submission requirements, which overlap in places but differ in the details.

Both stores update their rules every year. Treat any checklist, including this one, as a starting point, and confirm the latest Google Play submission requirements in Play Console and Apple's requirements in App Store Connect before you submit.

Google Play vs App Store Requirements at a Glance

The table compares the main mobile app publishing requirements on each platform.

Google Play Submission Requirements

These are the Google Play submission requirements to check before you upload your first build.

Developer Account and Verification

You need a Google Play developer account, which has a one-time registration fee of 25 US dollars. You must be at least 18, verify your identity, and choose a personal or organization account. The account type changes which Google Play submission requirements apply to you.

Testing Requirement for New Personal Accounts

This is the requirement that delays the most first-time launches. Personal developer accounts created after November 13, 2023, must run a closed test with at least 12 testers who stay opted in for at least 14 days in a row. Only then can you apply for production access, and Google says that review usually takes seven days or less. In practice, plan for at least three weeks between a finished build and a public release. Organization accounts don't have this requirement.

Target API Level and App Bundle

Since August 31, 2026, new apps and app updates must target Android 16 (API level 36) or higher. Existing apps must target Android 15 (API level 35) or higher to stay available to new users. Developers who need more time can request an extension in Play Console, which lets existing apps keep reaching all Google Play users until November 1, 2026. It is not a general delay of the deadline for new apps and updates. New apps must also be published as an Android App Bundle, not an APK. Of all the Google Play submission requirements, the target API level is the one that changes every year, so check it at the start of each release cycle.

Data Safety, Privacy Policy, and Account Deletion

Every app on Google Play, including apps that collect no user data, must complete the Data safety form and link to a privacy policy. If users can create an account in your app, Google also requires an in-app path to delete the account and its data, plus a web link where users can request deletion. Your Data safety answers must match what the app actually does.

Store Listing and Content Rating

Your listing needs an app name of 30 characters or less, a short description of up to 80 characters, a full description of up to 4,000 characters, an icon, a feature graphic, and screenshots. You also need to complete the content rating questionnaire and the target audience details in Play Console. These listing details are among the Google Play submission requirements reviewers check against the app itself.

App Store Submission Requirements

Apple's App Store submission requirements cover similar ground with different rules:

• Apple Developer Program. An active membership costs 99 US dollars per year.
• Current Xcode and SDK. Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later using the iOS 26 SDK or the matching platform SDK. Since September 9, 2026, iOS and iPadOS apps must also target iOS 13 or later, according to Apple's upcoming requirements page.
• Updated age rating. Apple introduced a new age rating system in 2025. Make sure your app has answered the updated age rating questions in App Store Connect, which Apple required by January 31, 2026, to avoid interruptions when submitting updates.
• Privacy details. Complete the App Privacy section, link to a privacy policy, and give every permission request a clear purpose string. Apps and third-party SDKs that use certain APIs must declare approved reasons in a privacy manifest.
• Account deletion. Under the Apple App Store review guidelines, apps that support account creation must offer account deletion within the app.
• Screenshots. Upload one to 10 screenshots per device size. The required sizes depend on the devices your app supports. For example, an iPhone app needs screenshots for Apple's large-display iPhone sizes, and an app that runs on iPad needs 13-inch iPad screenshots. Check Apple's current screenshot specifications before you export.
• App Review information. Provide a working demo account, contact details, and notes for any feature a reviewer can't easily test.

How to Publish an App on Google Play and the App Store

1. Set Up Developer Accounts Early

Register both developer accounts well before launch. Identity checks take time, and Google's testing rule for new personal accounts adds at least two weeks on its own.

2. Build for the Current Requirements

Set the Android target API level and the iOS Xcode and SDK versions to the current requirements. Review the latest Google Play submission requirements and Apple's requirements at the start of each release cycle, not the week of launch.

3. Complete Privacy and Compliance Details

Mobile app privacy requirements are where many submissions fail. Write a clear privacy policy, add account deletion if users can sign up, and make sure the Data safety form and App Privacy details match the app's real behavior.

4. Prepare Store Listing Assets

Create the name, descriptions, icon, screenshots, and preview videos for each store. Screenshots must show the real app.

5. Test With Real Users

Use Google Play's testing tracks and TestFlight on iOS. Fix crashes, broken links, and incomplete flows before you submit, since these are among the most common rejection reasons.

6. Submit, Respond, and Release

Submit with complete reviewer notes and a working demo account. If the app is rejected, fix the specific issue named in the reviewer's notes and reply through Play Console or App Store Connect. Once approved, release manually, on a schedule, or as a staged rollout.

Common Rejection Reasons and How to Avoid Them

Many rejections trace back to a missed rule, either one of the Google Play submission requirements or Apple's review guidelines. Apple lists the most frequent issues on its App Review page, and most apply to Google Play too:

• Crashes and bugs. Test on current devices and operating system versions.
• Incomplete information. Missing demo accounts or unclear review notes stop the review.
• Broken links and placeholder content. Every link must work, and all text and images must be final.
• Privacy gaps. Disclosures that don't match the app, or a missing account deletion option.
• Inaccurate listings. Screenshots and descriptions must match what the app actually does.
• Missed platform deadlines. On Google Play, an update that doesn't meet the current Google Play submission requirements for target API level can't be submitted.

Your 2026 App Launch Checklist

Work through this app launch checklist before every release. It combines the Google Play submission requirements and Apple's rules covered above:

How Bombay Softwares Helps US Businesses Launch Mobile Apps

Bombay Softwares builds Android and iOS apps for US companies and plans for the Google Play submission requirements and App Store rules from the start, so submission isn't a last-minute scramble.

• Healthcare: Prepare privacy disclosures and permission explanations carefully for apps that handle health data.
• Retail and E-commerce: Test checkout, payments, and account flows so reviewers can complete every key journey.
• Financial Services: Make sure the app is submitted by the right legal entity and that sensitive features are fully documented for reviewers.
• SaaS and Startups: Set up developer accounts and testing tracks early, so the first launch isn't delayed by account or testing rules.

Conclusion

Most app rejections come from preventable issues, and the Google Play submission requirements add one more risk for new developers: a testing period that can delay the first launch by weeks.

Set up both developer accounts early, build against the current target API level and Xcode version, keep privacy disclosures accurate, add account deletion where needed, and work through an app launch checklist before every release. Because the Google Play submission requirements and App Store submission requirements both change every year, confirm the latest rules in Play Console and App Store Connect before you submit.

If you're preparing to launch on Google Play and the App Store, Bombay Softwares can help you get the app and its submission ready.

Frequently Asked Questions

1. What are the Google Play submission requirements for a new app?
A: You need a verified Play Console account, an Android App Bundle that targets Android 16 (API level 36), a completed Data safety form, a privacy policy, account deletion if users can sign up, a content rating, and a full store listing. New personal accounts must also run a closed test with at least 12 testers for 14 days.

2. What are the App Store submission requirements?
A: You need an Apple Developer Program membership, an app built with Xcode 26 and the iOS 26 SDK, App Privacy details, a privacy policy, in-app account deletion if users can sign up, screenshots, an age rating, and complete App Review information.

3. How long does app review take?
A: Apple says it reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours. On Google Play, review times vary, and production access for new personal accounts is usually reviewed in seven days or less after the closed test. Neither timeline is guaranteed.

4. How much does it cost to publish an app on Google Play and the App Store?
A: Registering a developer account is the first of the Google Play submission requirements, and it costs 25 US dollars once. The Apple Developer Program costs 99 US dollars per year. Development, design, and testing costs are separate.

5. Do all new Google Play developers need 12 testers?
A: No. This part of the Google Play submission requirements applies only to personal developer accounts created after November 13, 2023. Organization accounts don't have to meet it before publishing to production.

6. Why do apps get rejected?
A: Common reasons include crashes and bugs, incomplete review information, broken links, placeholder content, privacy disclosures that don't match the app, inaccurate screenshots, and builds that miss the current Google Play submission requirements or Apple's SDK deadline.