An app launch checklist is the list of things Apple and Google check before your app goes live: developer accounts, a privacy policy, privacy disclosures, account deletion, a reviewer login, current build tools and an accurate store listing. Most of these are cheap to do early and expensive to bolt on at the end. Below, each requirement sits in the phase where you should deal with it, with a link to the official rule. Store rules change several times a year, so the date on each fact is when we last read the official page: November 11, 2026.
Why apps fail review
Apple publishes the answer. On its App Review page it says: "On average, over 40% of unresolved issues are related to guideline 2.1: App Completeness, which covers crashes, placeholder content, incomplete information, and more" (Apple App Review).
That is the pattern this checklist is built around. Apps rarely fail because a feature is missing. They fail because the parts nobody listed in the quote (the privacy pages, the deletion flow, the reviewer login, the listing) were left until submission week.
Phase 1: before you build
Open the developer accounts under the business
Both stores charge a fee and verify who you are. Do this first, because organization checks take time and everything else is published under these accounts.
- Apple: "The Apple Developer Program is 99 USD per membership year." An organization needs a legal entity (Apple does "not accept DBAs"), a D-U-N-S Number and a working website on its own domain (Apple enrollment).
- Google: "There is a US$25 one-time registration fee." You choose a Personal or an Organization account. "To create a developer account for an organization, you must provide a D-U-N-S number", and Google notes that applying for one through Dun & Bradstreet "is a completely free process". Organization accounts are required for financial, health, VPN and government apps (Play Console help 6112435, choosing an account type).
Open both yourself, under your business, not under your developer. If a developer publishes under their account, the app is theirs to move, keep or lose. Request the D-U-N-S number before anything else, because both organization sign-ups wait on it; our guide to getting a D-U-N-S number for the App Store and Google Play walks through it. For the Play Console side from sign-up to release, see how to publish an app on Google Play.
Declare your trader status on Google Play
Google's trader status declaration page, as read on 2026-11-11, says "all active developer accounts must declare whether they are a trader or non-trader" under EEA and UK law, and "This declaration must be completed by February 1, 2027, regardless of where apps are targeted or distributed." New accounts must declare "immediately upon account creation". Google's criteria include earning money from your apps and having "a legal status (such as a D-U-N-S number)", but it says it can't decide your status for you. Two details matter for a business:
- A trader on a personal account "must provide a contact phone number to be displayed on Google Play", and "your address will also be publicly displayed". That's one more reason to publish under an organization account.
- Missing the deadline "may trigger enforcement including app update blocks and removal from the Play Store globally."
More detail in Google Play trader status.
Know Google's 12-tester rule before you pick an account type
"Developers with personal accounts created after November 13, 2023, must run a closed test" with "a minimum of 12 testers who have been opted in continuously for at least 14 days". Only then "you can apply for production access" (Play Console help 14151465). Google states this for personal accounts. For a business, an organization account with a D-U-N-S number is the normal route. If you do use a personal account, line up your 12 testers now, not in launch week. More detail in Google Play's 12 testers rule.
Check the app is more than a website
Apple's guideline 4.2: "Your app should include features, content, and UI that elevate it beyond a repackaged website. If your app is not particularly useful, unique, or 'app-like,' it doesn't belong on the App Store." Google's spam policy says: "We do not allow apps that only have limited functionality and content" (Play Console help 9898783). If your plan is a web page inside an app shell, decide now what it does that the website doesn't.
Plan sign-in and payments against the rules
- Sign-in. Apple's guideline 4.8: apps that use "a third-party or social login service (such as Facebook Login, Google Sign-In …)" for the main account "must also offer as an equivalent option another login service" with privacy features Apple lists. Sign in with Apple qualifies, and is the usual answer. Apple said on August 24, 2026 that new Sign in with Apple addresses will be issued on private.icloud.com, and that apps "should ensure that their account systems, email validation logic, and allowlists accept addresses on the new private.icloud.com domain" as well as privaterelay.appleid.com (Apple news).
- Digital purchases. Apple's guideline 3.1.1: "If you want to unlock features or functionality within your app, (by way of example: subscriptions …), you must use in-app purchase." Google says apps "must use Google Play's billing system" for in-app purchases of features, content or goods, with listed exceptions (Google Play Payments policy).
- Physical goods and services. Apple's guideline 3.1.3(e): goods or services "consumed outside of the app" must use other methods, "such as Apple Pay or traditional credit card entry." Google doesn't require its billing system for physical goods or physical services such as transportation or cleaning.
- Link-outs in the US. Apple's 3.1.1(a) notes that link-out entitlements "are not required for developers to include buttons, external links, or other calls to action in their United States storefront apps."
- Apple Developer Program account opened by the business ($99 a year)
- Google Play developer account opened by the business ($25 once)
- D-U-N-S number requested first, for an organization account on both stores
- Google Play trader or non-trader status declared (every account, by February 1, 2027)
- If on a personal Google account: 12 testers lined up for a 14-day closed test
- A clear answer to what the app does beyond the website
- Sign in with Apple planned if any social login is used
- Each payment sorted into digital (store billing) or physical (card payments)
Phase 2: while you build
Build account deletion into the app
Apple's guideline 5.1.1(v): "If your app supports account creation, you must also offer account deletion within the app." Apple's account deletion page adds that "only offering to temporarily deactivate or disable an account is insufficient", that apps outside highly regulated industries "should not require people to make a phone call, send an email … or go through other support flows", and that Sign in with Apple apps "should use the Sign in with Apple REST API to revoke user tokens."
Google asks for two routes: "an in-app path to delete their app accounts and associated data" and "a web link resource where users can request app account deletion". You "must also delete the user data associated with that app account", and any data you keep must be disclosed (Play Console help 13327111). In practice that means a delete button in settings and a page such as /delete-account on your website. See account deletion requirements.
Put the privacy policy in the app
Apple's guideline 5.1.1(i): "All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner." The policy must also "Explain its data retention/deletion policies". Write it from a real list of what the app collects, including what each third-party SDK collects, because the same list feeds the store forms in Phase 3.
Use current build tools
- Apple: since April 28, 2026, "Apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26". Since September 9, 2026, iOS and iPadOS apps "must target iOS 13 or later". Since May 1, 2024, you must "include approved reasons for the listed APIs used by your app's code (including from third-party SDKs)" to upload a new or updated app; those reasons go in a privacy manifest (Apple upcoming requirements).
- Google: since August 31, 2026, "New apps and app updates must target Android 16 (API level 36) or higher to be submitted to Google Play" (Play Console help 11926878).
Finish everything the reviewer will touch
Guideline 2.1 also covers purchases: "If you offer in-app purchases in your app, make sure they are complete, up-to-date, visible to the reviewer and functional." No "coming soon" screens, no lorem ipsum, no dead links. Apple's guideline 1.5 asks that "your app and its Support URL include an easy way to contact you."
- Delete account in the app's settings, removing the account and its data
- A public web page where users can request account deletion
- Sign in with Apple tokens revoked on deletion
- Sign-up and email checks accept private.icloud.com relay addresses
- Privacy policy written from a real list of collected data, linked inside the app
- iOS build made with Xcode 26 and the iOS 26 SDK, with privacy manifests
- Android build targeting API level 36
- In-app purchases complete and testable
- No placeholder text, empty screens or broken links
- A contact route inside the app
Phase 3: before you submit
Fill in the privacy forms
- Apple: your App Store Connect privacy details are part of your metadata. Guideline 2.3 says metadata, "including privacy information", must accurately reflect the app and be kept "up-to-date with new versions".
- Google: "All developers that have an app published on Google Play must complete the Data safety form", on closed, open and production tracks. "Even developers with apps that do not collect any user data must complete this form and provide a link to their privacy policy" (Play Console help 10787469).
Give the reviewer a way in
Apple wants demo account details and a running backend (guideline 2.1). Google: "If your entire app or parts of your app are restricted based on login credentials … you must provide all required details to enable access to your app" (Play Console help 9859455). Use a dedicated reviewer account with sample data, and check it works on the live backend the day you submit.
Prepare the store listing
Apple's guideline 2.3.3: "Screenshots should show the app in use, and not merely the title art, login page, or splash screen." Description, screenshots and previews must reflect "the app's core experience". On Google Play, the target age group and the content rating questionnaire are required (help 9859455).
Answer Apple's age-rating questions, including the new ones
Apple's age-rating questionnaire grew twice in 2026. Since September 2026, answers to its new social media questions are "required when submitting new apps or updates to the App Store" (Apple news, July 9, 2026). From November 16, 2026 you also declare whether the app includes "Shared Location" or "Dating and Relationships": "All apps must have these declarations completed by January 12, 2027", and apps with Dating and Relationships "receive a minimum age rating of 18+" (Apple news, November 2, 2026). Apple's guideline 2.3.6 asks you to "Answer the age rating questions in App Store Connect honestly". Our guide to App Store age ratings explains the questionnaire, and app age verification laws covers the laws around it.
- Apple privacy details and Google Data safety form completed from the same data list
- Privacy policy URL in both store listings
- Support URL with a working contact method
- Reviewer login and notes for both stores, tested on the live backend
- Screenshots that show the app in use
- Description that matches what the app actually does
- Google content rating questionnaire and target age group done
- Apple age-rating questions answered, including social media, Shared Location and Dating and Relationships
Phase 4: submission
Apple says App Review is "typically reviewing at least 50% of submissions in less than 24 hours and 90% in less than 48 hours" (Apple App Review). On Google Play, a personal account created after November 13, 2023 applies for production access only after the 14-day closed test. To plan a launch date around review, see how long App Store review takes.
If either store rejects the app, read the message closely. It names the guideline or policy. Fix that issue, reply in the review thread with what changed, and resubmit. Our guide to app store rejection walks through the common guideline numbers, and how to appeal an App Store rejection covers the rarer case where the reviewer got it wrong.
Phase 5: after approval
Getting approved once doesn't keep you approved. Both stores move their requirements every year:
- Google target API: "Existing apps must target Android 15 (API level 35) or higher to remain available to new users" (help 11926878). Expect the bar to rise each year.
- 16 KB page sizes: "Starting February 1, 2027, if your app updates don't support 16 KB memory page sizes, you won't be able to release these updates" for apps targeting Android 15 or higher (Android page sizes).
- Android developer verification: protections began September 30, 2026 in Brazil, Indonesia, Singapore and Thailand, and will be "expanded globally … in 2027". Google says "Google Play automatically registers 99% of apps" (Android developer verification).
- Apple SDK rules: Apple raises the required Xcode and SDK version on its upcoming requirements page. Check it before each release. Next: "Starting April 2027", "iOS and iPadOS apps must be built with the iOS 27 & iPadOS 27 SDK or later" (Apple news, September 9, 2026).
- No features added outside review: Apple's new guideline 2.5.19 (October 16, 2026) says "Don't include any hidden, dormant, or undocumented features in your app". Apple says it targets apps "misrepresenting what they do during the App Review process and then changing after approval", for example by "adding features or functionality that weren't included in the version of the app that was submitted to App Review" (Apple news). Ship new features as reviewed updates, even if your app could load them from the web.
- Apple's spam rule: guideline 4.3(b), revised on June 8, 2026, now says of well-established kinds of apps such as dating, flashlight and wallpaper apps: "We may remove these apps from the App Store going forward if they are not updated, improved, or do not attract customers."
- Privacy disclosures: when an update adds a new SDK or collects new data, update the privacy policy, Apple's privacy details and the Data safety form in the same release.
For Google's dated requirements in one place, see Google Play deadlines.
Every requirement, with the Apple and Google rule
| Requirement | Apple | Google Play | Official source |
|---|---|---|---|
| Developer account | $99 a year; organizations need a legal entity, D-U-N-S and own-domain website | $25 once; organization accounts need D-U-N-S | Apple · Google |
| Trader status | EU only: apps without it are removed from the EU App Store | Every account declares by Feb 1, 2027, wherever it distributes | Apple · Google 17594752 |
| Testing before production | No matching rule in the pages we checked | Personal accounts after Nov 13, 2023: 12 testers, 14 days | Google 14151465 |
| App completeness | 2.1: final build, no placeholders, no crashes | Reviewer access to restricted parts | Apple 2.1 · Google 9859455 |
| Minimum functionality | 4.2: more than a repackaged website | No apps with only limited functionality and content | Apple 4.2 · Google 9898783 |
| Sign-in | 4.8: equivalent login option if social login is used; accept private.icloud.com relay addresses | No matching rule in the pages we checked | Apple 4.8 · Apple relay domain |
| Privacy policy | 5.1.1(i): in metadata and inside the app | Linked in the Data safety form, even with no data collected | Apple 5.1.1 · Google 10787469 |
| Privacy disclosures | 2.3: privacy information accurate and current | Data safety form on every track | Apple 2.3 · Google 10787469 |
| Account deletion | 5.1.1(v): in the app; no deactivate-only; revoke Sign in with Apple tokens | In-app path plus a web link; delete the data | Apple · Google 13327111 |
| Reviewer login | 2.1: demo account, backend on | Provide all details needed for access | Apple 2.1 · Google 9859455 |
| Build tools | Xcode 26 and iOS 26 SDK; target iOS 13+ | New apps and updates target API 36 | Apple · Google 11926878 |
| Payments | 3.1.1: in-app purchase for digital unlocks; 3.1.3(e): card payments for physical goods | Play billing for digital items; exceptions for physical goods and services | Apple 3.1 · Google 9858738 |
| Store listing | 2.3.3: screenshots show the app in use | Content rating and target age group | Apple 2.3 · Google 9859455 |
| Age rating | Questionnaire, plus Shared Location and Dating and Relationships declarations by Jan 12, 2027 | Content rating questionnaire | Apple · Google 9859455 |
| Support contact | 1.5: easy contact in the app and Support URL | No matching rule in the pages we checked | Apple 1.5 |
If someone else is building your app
Ask your developer which of these items are in their quote, and who opens the accounts. Many fixed-price quotes list screens and features but not the deletion flow, the privacy pages or the reviewer setup, and those are what reviewers check. If an AI tool wrote the app, run the security checklist for vibe-coded apps before you submit: App Review tests what the reviewer can see, not who can read your database. If your app is already built and stuck, App Rescue covers store submission and launch fixes on their own.
At PerceptiaAI, the store work on this list is part of the launch kit in every build: the privacy policy and terms, privacy labels and Data safety, a support page and /delete-account, the reviewer login, a 12-tester plan for Google Play, and submission to both stores. You can see what else is included in every build.
Changelog
- 2026-11-11: Added Google Play's trader status declaration (due February 1, 2027) to Phase 1, its checklist and the requirements table.
- 2026-11-11: Replaced the January 2026 age-rating note with Apple's social media questions and the Shared Location and Dating and Relationships declarations due January 12, 2027.
- 2026-11-11: Added Apple's new Sign in with Apple relay domain, the June 2026 revision of guideline 4.3 and Google's April 2026 Account Transfer policy.
- 2026-11-11: Added Apple's new guideline 2.5.19 (October 16, 2026) and the iOS 27 SDK requirement from April 2027.
- 2026-11-11: Corrected two quotes to match the current pages: Google's D-U-N-S line now reads "must provide", and Apple's privacy-manifest requirement is quoted in its own words.
- 2026-11-11: Rechecked every official source; Google's API level 36 requirement is now in force.
