Checklist · Build and earn
App Store and Google Play Launch Checklist
Opens with creditsA step-by-step checklist for publishing a mobile app on the Apple App Store and Google Play for the first time, or for a client. It covers developer accounts, current build requirements, the review guidelines that cause most rejections, privacy labels and the Data safety form, store listing and screenshots, in-app purchase rules, testing tracks, crash reporting and phased or staged rollout, checked against Apple and Google documentation in October 2026.
Written by Tauseef Fayyaz9 chapters, 37 checksAbout 27 minReviewed 13 October 2026What you will learn
9 chapters · about 27 min
1Developer accountsSet up the right accounts early. Enrolment and verification can take days, and Google Play adds a testing requirement for new personal accounts.5 checks · 4 min
- 1Decide who owns the developer accounts: you or the client
- 2Enrol in the Apple Developer Program and budget for the annual fee
- 3Register a Google Play developer account and complete identity verification
- 4For a new personal Play account, plan for 12 testers over 14 days before production
- 5Declare your EU trader status in App Store Connect
5 in this chapterOpen this chapter2Build and platform requirementsBoth stores reject builds that miss current SDK and API level rules. Check them before your final build, not after it is rejected.4 checks · 3 min
- Pass review the first timeMost rejections come from a short list of avoidable problems. Check these before you press submit.5 checks · 4 minOpens with credits
- Privacy labels, Data safety and permissionsBoth stores show users what data your app collects. The answers must cover every SDK, match your privacy policy and stay current.4 checks · 3 minOpens with credits
- Store listing and screenshotsThe listing is what turns a store visit into an install. Meet each store's limits and show the app actually being used.5 checks · 3 minOpens with credits
- In-app purchases and paymentsSelling digital features follows strict store rules. Pick the right payment method for what you sell before you build checkout.4 checks · 3 minOpens with credits
- Beta testing tracksTest with real users on real devices before the public sees the app. Both stores provide tracks for this.3 checks · 2 minOpens with credits
- Crash reporting and stabilityFind out about crashes from your tools, not from one-star reviews. Google Play also uses stability to decide how visible your app is.3 checks · 2 minOpens with credits
- Release and staged rolloutRelease gradually so a bad build reaches few users. Both stores support this for updates, with different rules.4 checks · 3 minOpens with credits
About this checklist
An app store launch checklist matters because the stores reject or delay apps for reasons that have nothing to do with code quality: a missing demo account, a privacy label that does not match an analytics SDK, a screenshot that shows a splash screen, a subscription sold outside in-app purchase, or a new Google Play account that has not run the required closed test. Each one can cost days, and some cost weeks.
This checklist follows a launch in order. The first chapters cover the developer accounts on both stores and the current build requirements, such as Apple's minimum Xcode and SDK versions and Google Play's target API level. The middle chapters cover the review guidelines behind most rejections, privacy disclosures on both stores, the store listing and screenshots, and the rules for selling digital goods. The last chapters cover testing tracks such as TestFlight and Play closed testing, crash reporting and stability thresholds, and releasing gradually with Apple's phased release and Google Play's staged rollouts.
The checks are based on Apple's App Store Review Guidelines and App Store Connect help, and Google's Play Console help and Android developer documentation, as of October 2026. Store requirements change several times a year, so each check tells you where to confirm the current rule. It works whether you are launching your own indie app or publishing for a freelance client, and whether you built it with Swift, Kotlin, Flutter or React Native.
Common questions
How much does it cost to publish an app on the App Store and Google Play?
Apple lists the Apple Developer Program at 99 USD a year, and Google Play lists a one-time 25 USD registration fee. Both stores also take a commission on paid apps and in-app purchases, with reduced rates in programmes such as Apple's Small Business Program. Check both stores' own pages for current figures.
Why does Google Play need 12 testers for 14 days?
Google Play requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers opted in continuously for at least 14 days before applying for production access. Organisation accounts are not covered by this rule.
How long does App Store review take?
Apple says it typically reviews at least 50% of submissions in under 24 hours and 90% in under 48 hours. Incomplete submissions take longer, so make sure the demo account, backend and metadata are ready before you submit.
What is the most common reason apps are rejected by Apple?
Apple says over 40% of unresolved issues relate to guideline 2.1, App Completeness: crashes, placeholder content, broken links and missing information such as demo account details.
Can I use Stripe or my own payments for in-app subscriptions?
Not for digital features in most cases. Apple requires in-app purchase to unlock digital features and content, and Google Play requires its billing system for digital goods, with exceptions such as physical goods and some person-to-person services, plus regional programmes. Read the guidelines for each storefront you sell in.
Do I need a privacy policy if my app collects no data?
Yes on both stores in practice. Apple requires a privacy policy link for all apps, and Google requires a privacy policy to complete the Data safety form even if the app collects no user data.
Sources (8)
Checked against these, last on 13 October 2026.
- App Review Guidelines, Apple Developerdeveloper.apple.com/app-store/review/guidelines/
- App Review, Apple Developerdeveloper.apple.com/distribute/app-review/
- Upcoming requirements, Apple Developerdeveloper.apple.com/news/upcoming-requirements/
- App privacy details on the App Store, Apple Developerdeveloper.apple.com/app-store/app-privacy-details/
- Release a version update in phases, App Store Connect Helpdeveloper.apple.com/help/app-store-connect/update-your-app/release-a-version-update-in-phases/
- App testing requirements for new personal developer accounts, Play Console Helpsupport.google.com/googleplay/android-developer/answer/14151465
- Provide information for Google Play's Data safety section, Play Console Helpsupport.google.com/googleplay/android-developer/answer/10787469
- Meet Google Play's target API level requirement, Android Developersdeveloper.android.com/google/play/requirements/target-sdk
Related on Sefism
Picked from the other libraries by shared topics.
Best practices
See all- React Native Best PracticesReact Native best practices for 2026: Expo and the New Architecture, fast lists, smooth animations, safe storage, deep links, accessibility and release builds.
- Flutter Best PracticesFlutter best practices for 2026: sound null safety, cheap build methods, layered architecture, smooth frames, go_router, accessibility, testing and safe releases.
Checklists
See all- Mobile App Security ChecklistCheck an Android or iOS app against OWASP MASVS: data storage, network security, authentication, platform interaction, code quality, resilience and privacy.
- Selling Digital Products Checklist for DevelopersSell templates, starter kits, e-books, courses or plugins the safe way: product choice, licensing, platforms, merchant of record, pricing, delivery, refunds, taxes, marketing and updates.
Project structures
See all- Flutter project structureFor anyone building one Dart app for Android, iOS and the web. The tree starts from what flutter create gives you and grows into a feature-first lib/ folder, where each feature keeps its own data, domain and presentation code, then adds tests at every level, flavors, release signing, crash reporting and, for large teams, a melos workspace of local packages.
- React Native with Expo project structureFor web developers who know React and want one TypeScript codebase for Android, iOS and the web. Routes are files in src/app (Expo Router), the business logic lives in feature folders under src/features split into data, domain and presentation, and the native android and ios folders are generated, not hand-written.
- Android with Kotlin and Compose project structureFor anyone building a native Android app the way Google recommends in 2026: Kotlin, Jetpack Compose, a ViewModel per screen, repositories over Room and the network, and Hilt wiring it together. The tree starts from Android Studio's Empty Activity template, grows into feature packages with data, domain and presentation, adds signing, shrinking, CI and crash reporting for production, and ends as a multi-module build with convention plugins, Baseline Profiles and staged rollouts.
Career questions
See allStuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com