Category
Guide
Subject
App Store publication
Reading time
14 minutes
Level
Founder & product
Updated
May 2026

Minimum app requirements for the App Store and Google Play.

A complete guide to the technical, legal and operational requirements an iOS or Android app must meet to actually get published in 2026. For founders, product owners and marketing teams preparing a launch.

App Store (iOS) — minimum requirements

Apple operates a closed ecosystem. Anyone who wants to publish has to get through a review process and a list of technical requirements that gets stricter every year. We go through them below in order of practical relevance.

Account and toolchain

  • Apple Developer Program — a paid annual subscription tied to an Apple ID, in the name of your organisation or as an individual. For businesses we recommend the organisation option, as it lets you add multiple team members to a single account.
  • App Store Connect — the portal where you upload builds, fill in metadata and submit apps for review. Access runs through your developer account.
  • Xcode — Apple's IDE. For a few years now, Apple has required builds to be made with the latest version of Xcode or one version back. A build made with an outdated Xcode is rejected on upload.
  • iOS SDK — the SDK version is tied to Xcode. Each autumn, Apple announces which minimum SDK becomes mandatory for new submissions from the following April.

Privacy and data

Since iOS 14.5, privacy requirements have been the biggest stumbling block at submission. There are three mandatory components:

  • App Privacy details — the so-called "privacy nutrition labels". For each type of data (location, contacts, browsing history, financial, health), you must state whether you collect it, for what purpose, and whether it is linked to the user.
  • App Tracking Transparency (ATT) — if your app uses tracking data for advertising or shares it with third parties, an ATT prompt is mandatory. The user must explicitly opt in.
  • Sign In with Apple — if you offer social login (Google, Facebook, etc.), Sign In with Apple must be offered on an equal footing. Offering other providers without "Sign in with Apple" means automatic rejection.

Security and networking

  • ATS (App Transport Security) — all network traffic must use HTTPS. Unencrypted HTTP is only allowed with an explicit exception in Info.plist and a sound justification.
  • Code signing — every build is signed with a Distribution certificate from your developer account. Provisioning profiles determine which devices and which entitlements are permitted.
  • App Sandbox & entitlements — access to the camera, microphone, location, contacts, photo library, push, HealthKit and so on must be explicitly requested as an entitlement and explained in the UX through the "purpose strings" (NSCameraUsageDescription and so on).

Review guidelines

Apple's App Review Guidelines are divided into five main sections: Safety, Performance, Business, Design and Legal. About 90% of rejections fall into one of these categories — usually Performance (crashes during review) or Business (in-app purchases not going through StoreKit). The full guidelines are on Apple's developer site and are updated a few times a year on average.

Distribution and testing

  • TestFlight — Apple's beta distribution channel. Up to 100 internal testers (without review) and up to 10,000 external testers (with a light beta review). Essential for any serious beta.
  • App size — Apple uses "app thinning" and asset catalogues to reduce the download size per device. The upload binary can be large, but Apple generates smaller device-specific variants.
  • Family Sharing — optional, but recommended for consumer apps: it lets a single purchase be shared within a family.

UX and accessibility

Accessibility is no longer a nice-to-have. Apple increasingly rejects apps that ignore VoiceOver entirely, especially if they are also used in the public sector or healthcare. The minimum level is VoiceOver labels on all interactive elements, support for Dynamic Type (users can set their own text size), and correct contrast ratios. For more background on app choices early in the process, our app development service page is a good place to start.

Monetisation

Digital goods (subscriptions, in-app content, virtual currency) must go through StoreKit. Apple's commission on these is a fact you need to factor in. Physical goods and services may use external payment channels (Stripe, Mollie, iDEAL), but the distinction between digital and physical must be crystal clear.

Google Play (Android) — minimum requirements

Google Play is technically more tolerant than the App Store, but it now has a similarly dense set of policy requirements. The biggest pitfalls are in the privacy policy and the Data Safety section, which is where most rejections happen.

Account and console

  • Google Play Developer Account: a one-off registration fee and verification of your identity (mandatory for all new accounts since 2024).
  • Play Console: Google's portal for publishing, releases, statistics and policy notifications.

SDK and API requirements

  • Target SDK: Google requires new apps and updates to target an API level that is at most two versions behind the latest Android release. The minimum target moves up every autumn. Don't underestimate this: even apps that have been in the store for a long time have to keep up.
  • minSdkVersion and compileSdkVersion: minSdk determines which older Android versions you still support, while compileSdk determines which APIs you can call in code. For consumer apps we typically see minSdk 24 (Android 7) or higher.
  • Android App Bundle (AAB): since August 2021, the AAB has been mandatory for new apps. Google no longer accepts standalone APKs. Google generates an optimised APK per device from your AAB.
  • Play App Signing: Google hosts your upload key and signing key. If you lose the upload key, you can recover it through a reset flow, and the signing key itself stays safe.

Privacy and data safety

  • Privacy Policy URL: mandatory. It must be accessible on your own domain, written in clear language with clearly defined data categories. A placeholder or "coming soon" page is an immediate rejection.
  • Data Safety section: required since 2022. For each data type, you declare whether you collect it, whether you share it, and whether it is optional. A mismatch between the privacy policy and the Data Safety form is by far the biggest source of rejections on Google Play.
  • Permissions: every permission you request must either be functionally justified or removed. Sensitive permissions (background location, SMS, call log, accessibility services) require a separate declaration in the Play Console.

Content and target audience

  • Content rating (IARC): a questionnaire that classifies your app per region (PEGI in Europe, ESRB in the US).
  • Target audience & content: if your app targets children, COPPA (US) and GDPR-K (EU) apply, plus Google's "Designed for Families" policy.

Recent Android features that affect the checklist

  • Notification permission (Android 13+): push notifications require a runtime permission. The flow needs to fit logically into the onboarding.
  • Foreground service types (Android 14+): if you do work in the background, you must explicitly declare why (location, media playback, dataSync, etc.).
  • Photo Picker (Android 13+): Google encourages using the system Photo Picker instead of a blanket photo permission.
  • Play Integrity API: an anti-fraud check that verifies your app is running on a genuine, non-rooted device and that the binary has not been tampered with. For financial and healthcare apps, it is now effectively mandatory.

Common reasons for rejection

Most first submissions are rejected, and almost always for the same reasons. Here is an overview of what we see most often in practice.

iOS: top reasons for rejection

  • Weak metadata: screenshots that don't match the current app UI, a title or keywords that promise more than the app delivers, or marketing claims without substantiation.
  • Copycat design: UI patterns that are too close to a well-known app (Apple calls this "minimum functionality" or "spam").
  • Privacy policy gaps: privacy nutrition labels that don't match what the app actually does.
  • Broken functionality during review: Apple's reviewer can't log in, a feature crashes, or a third-party API returns a 500 error. Always provide a working test account via "App Review Information".
  • Missing ATT prompt: you collect advertising data without asking the user for permission.
  • Private APIs — use of undocumented Apple APIs. Almost always detected automatically on upload.

Android — top rejection reasons

  • Privacy policy mismatch — what the policy says doesn't cover what the app does.
  • Undisclosed data collection — third-party SDKs (analytics, attribution, ads) that send data not listed in the Data Safety form.
  • Sensitive permissions without use — you request SMS or accessibility access but don't visibly use it.
  • Dark patterns — subscription traps, misleading UI, forced reviews.
  • Misleading content or impersonation — name, icon or description resembles another well-known app or brand.

Pre-submission checklist

Our advice: work through this list at least two sprints before you submit. Many teams underestimate that a good submission is a mini-project in its own right.

  • Test on multiple devices — at least two iPhone generations and two Android manufacturers (Samsung and Pixel as a baseline, plus a Xiaomi or OnePlus for edge cases).
  • Privacy policy live — on your own domain, with the date of the last update.
  • App Store screenshots — for every required device size. Apple requires screenshots for the largest iPhone and iPad. Google has its own set for phone, 7" tablet and 10" tablet.
  • Description — a short description (80 characters) plus a full description (4,000 characters). Optimised for your most important search terms.
  • Localisation — for EU markets, at least NL and EN, often DE and FR as well. Translate not only the UI but also the store listing.
  • Crash rate — below 0.5% for a healthy release. Firebase Crashlytics or a comparable tool is effectively indispensable.
  • ANR rate (Android) — "Application Not Responding" events also below 0.5%. Play Console monitors this and will downrank apps that exceed the threshold.
  • App icon — in all required sizes (Apple generates them from a single hi-res file; Android wants explicit maskable icons).
  • Splash screen — short and functional. Apple rejects excessively long splash screens.
  • Onboarding flow — the first-launch experience. Don't push permissions on the first screens.
  • Support email — working and monitored. A mailbox that goes unanswered is a rejection trigger.
i
In practice

The first submission is rarely approved in one go. Expect one to three iterations with the reviewer before the app goes live. Important: use the time between submissions productively — don't wait, but start preparing the next round straight away.

Compliance overlays

On top of the store requirements sits a layer of laws and regulations that varies by market and sector. The relevant ones:

  • EU Digital Services Act (DSA) — in force since February 2024. Particularly relevant for apps with user-generated content or marketplace functionality: reporting mechanisms, transparency about moderation, a point of contact for authorities.
  • EU AI Act — being phased in. Apps with AI features must be transparent about what the AI does, what data it uses and what risks are involved. Stricter requirements apply to high-risk applications (healthcare, HR, credit).
  • GDPR — data processing agreements with all SDK providers, a DPIA for sensitive data, and user rights (access, erasure, data portability) properly handled in the app or via the web.
  • COPPA — mandatory in the US for apps aimed at children under 13. In practice combined with Google's "Designed for Families" and Apple's "Made for Kids".
  • NEN 7510 or HIPAA — for healthcare apps in the Netherlands and the US respectively. Requires its own security framework and regular audits.

For a B2C launch with international ambitions, this list is one of the main reasons to involve a privacy lawyer early. Apps aimed at business customers have their own set of requirements, which our B2B app development page covers in more depth. For consumer apps, the B2C version is the right place to start.

Updates and maintenance after launch

The launch is not the end — it is the beginning. Don't underestimate the ongoing maintenance workload, because both Apple and Google force you to keep updating.

Target version cycle

Apple requires a new minimum target every autumn, and Google does the same in August/September. Apps that don't keep up either become invisible in the store to new users or are removed entirely after a few years of inactivity. Expect to update your app at least once a year just to meet the target version.

OS support strategy

How many older OS versions you support is a product decision with a direct impact on your cost base. Two versions back is the industry standard; three versions is rarely done unless you have a large installed base. Going further back only makes sense if your target group has hard outliers (healthcare, government).

Security updates and library monitoring

Third-party libraries have vulnerabilities. A good release cycle includes automated scans (Dependabot, Snyk, Renovate) plus an update sprint at least once a quarter in which you apply critical updates. This belongs in the scope of every ongoing app maintenance relationship.

We explain what a new app realistically costs and which factors determine the rate in our guide to custom software costs. You can find an overview of all guides and knowledge base articles on the guides overview page.

Frequently asked questions

Can I publish an iOS app without a Mac?

Technically yes, but in practice it's not advisable. Xcode only runs on macOS, and all signing, archiving and upload steps go through it. Cloud build services (Codemagic, Bitrise, Xcode Cloud) run on Macs in data centres under the hood and are a lifesaver for some teams, but local debugging still requires a Mac. For serious app work, a Mac is indispensable.

How long does Apple's review take?

For a first submission, expect several days; for updates, usually within 24 hours. Public holidays, major OS releases (September) or a question from the reviewer can cause delays. Never plan a launch for a fixed date without a buffer.

Write the privacy policy yourself or get it done for you?

For a simple app that collects little data, you can start with a template and adapt it to your app, as long as you understand what it actually says. For apps with user accounts, third-party SDKs or payment flows, a privacy lawyer (or a specialist service such as Iubenda) is worth the investment. The Data Safety form on Play and the Privacy Nutrition labels on iOS must match the policy exactly.

TestFlight versus internal testing on Google Play?

Functionally comparable: a closed beta environment for early testers. TestFlight is more polished and has a separate iOS app for testers. Google's internal and closed testing tracks work via a mailing link and the regular Play Store. For a first launch, use both for at least two weeks of internal testing before you expand externally.

App Bundle (AAB) or APK?

New apps must upload an AAB. The APK still exists for distribution outside Google Play (sideloading, alternative stores) and for internal enterprise distribution. For Play Store publication you have no choice: AAB is mandatory.

What do I do if Apple or Google rejects my app?

Read the rejection note carefully and see which guideline or policy is cited. Nine out of ten rejections can be resolved quickly with a small change. Reply to the reviewer politely and professionally via App Store Connect or Play Console. If you disagree, you can appeal: with Apple via the Resolution Center, with Google via an appeal form. Expect a few rounds of correspondence in any case.

What do developer accounts cost?

Apple charges an annual subscription, Google a one-off registration fee. Both amounts are negligible compared with the total budget of an app project, so there is no reason to base your choice of platform on them.

How often do I need to update my app?

At least once a year for the target version. In practice, active apps release every two to four weeks: feature updates, bug fixes and security patches. For a supporting product app without much ongoing development, a quarterly update cycle is realistic.

The three key points.

01

Privacy is the toughest requirement

On both iOS and Android, the privacy policy and data declaration are the biggest source of rejections. Any mismatch between what you say and what the app does is penalised immediately.

02

Target versions move on every year

Apple and Google force you to keep updating. Launching an app is not a one-off: plan for a fixed annual update round for compliance alone.

03

The first submission rarely passes

Expect one to three iterations with the reviewer. Build that time into your planning and always provide a working test account.

Talk to us about your app launch.

A half-hour introductory call. We walk through your app or plan, flag the biggest publication risks and give you an honest estimate of what it takes to get the first submission right first time.

Edit content