Free Checklist · 2025

Mobile App Launch Checklist

A complete iOS and Android pre-launch checklist covering product readiness, performance, security, App Store and Google Play submission, ASO, onboarding, monetisation, analytics, legal compliance, and post-launch — 160+ items across 11 categories.

▸ How to use this checklist

Start at least 4 weeks before your target launch date. Critical items are non-negotiable — missing them leads to store rejection or catastrophic post-launch issues. Complete High items before submission. Medium items should be addressed in your first update sprint.

160+

Checklist Items

11

Categories

iOS + Android

Both Platforms

Free

No signup needed

Priority Key:
Critical
High
Medium
160+ items · 11 categories · iOS & Android
Launch Timeline

4-Week Launch Countdown

Apple and Google review times mean you cannot submit at the last minute. Work backwards from your launch date using this timeline.

T-4 Weeks
Complete product testing on real devices
Set up analytics and crash reporting
Draft store listing copy and screenshots
Create developer accounts if not yet done
T-2 Weeks
Submit to TestFlight (iOS) and internal track (Android)
Complete all privacy declarations and legal pages
Finalise in-app purchase configuration
Begin ASO keyword research
T-1 Week
Submit to App Store review (iOS)
Upload to Google Play production track (Android)
Prepare launch day communications
Set up monitoring alerts and response plan
Launch Day
Monitor crash rate every hour
Respond to every early review
Post on Product Hunt and communities
Begin first push notification campaign
Quick Reference

App Store vs Google Play — Key Differences

Understanding the differences between platforms prevents last-minute surprises during submission.

Aspect
🍎App Store (iOS)
🤖Google Play
Review Timeline
1–3 business days (plan 2 weeks)
1–7 days (plan 1 week)
Developer Account Cost
$99/year (Apple Developer Program)
$25 one-time fee
Screenshots Required
Min 1, max 10 per device size
Min 2, max 8 per device type
App Size Limit (OTA)
200MB over cellular
150MB APK, 2GB with AAB
Rejection Rate
Higher — strict human review
Lower — mostly automated
In-App Purchase Cut
15–30% (15% for small business)
15–30% (15% for first $1M)
Beta Testing
TestFlight (up to 10,000 testers)
Internal/closed/open tracks
Update Approval
Usually 1–2 days
Usually same day
📱
01
Category

Product & Feature Readiness

Your app must work reliably across all target devices and OS versions before submitting to either store. A buggy first impression is nearly impossible to recover from in reviews.

15Items
Core user flows tested end-to-end on real devices — not just simulatorsCritical
App tested on minimum supported iOS version (iOS 16+) and Android API level (API 26+)Critical
App tested on at least 3 different screen sizes per platform (small, medium, large)Critical
All navigation flows work correctly — no dead ends, broken back buttons, or missing screensCritical
Empty states designed and implemented — new users see helpful prompts, not blank screensCritical
Error states handled gracefully — network errors, API failures, and empty data all show meaningful messagesCritical
Offline behaviour defined and tested — app handles no connectivity without crashingCritical
Dark mode fully supported and tested on both iOS and AndroidHigh
Dynamic type / font scaling tested — large accessibility text sizes do not break layoutsHigh
Landscape orientation handled if app supports it — no broken layouts when device rotatedHigh
App icon displays correctly at all required sizes (20pt to 1024pt on iOS, 48dp to 512px on Android)High
Splash screen / launch screen displays correctly and does not stay visible too longHigh
iPad layout tested if app supports iPad (universal app)Medium
Haptic feedback used appropriately for key interactions on iOSMedium
Right-to-left (RTL) language layout tested if targeting Arabic or Hebrew marketsMedium
7 critical · 5 high · 3 medium
02
Category

Performance & Stability

Users abandon slow and crashy apps immediately and leave one-star reviews. Performance must be measured on low-end devices, not just the latest flagship hardware.

13Items
Crash rate under 0.1% — verified in pre-launch testing with Firebase Crashlytics or SentryCritical
App launches from cold start in under 2 seconds on mid-range deviceCritical
No ANR (App Not Responding) errors on Android — all heavy operations run off the main threadCritical
Memory usage stable over time — no memory leaks causing the app to slow down or crash after extended useCritical
Network requests handle timeout and retry correctly — no infinite loading statesCritical
App performance tested on a low-end Android device (2GB RAM, budget chipset) — not just flagship devicesHigh
List views with large datasets use virtualisation / lazy loading — no full data load into memoryHigh
Images properly cached — same image does not re-download on every viewHigh
Battery drain acceptable — app does not cause abnormal battery usage in backgroundHigh
App binary size optimised — remove unused assets, use vector icons, compress imagesHigh
Frame rate stable at 60fps during animations and scrolling — no janky UI transitionsMedium
Background fetch and push notification handling tested — does not wake app unnecessarilyMedium
Deeplink performance tested — app opens and navigates to correct screen within 1 secondMedium
5 critical · 5 high · 3 medium
🔒
03
Category

Security & Privacy

Both Apple and Google enforce strict privacy requirements. Missing privacy declarations or requesting unnecessary permissions will get your app rejected in review.

15Items
All API communications use HTTPS — no plain HTTP requests in production buildsCritical
App Transport Security (ATS) enabled on iOS — exceptions documented and justifiedCritical
No sensitive data (API keys, credentials, PII) hardcoded in the app binaryCritical
Authentication tokens stored in Keychain (iOS) or EncryptedSharedPreferences / Keystore (Android)Critical
Privacy Policy URL provided in App Store Connect and Google Play ConsoleCritical
Apple Privacy Nutrition Labels accurately completed in App Store ConnectCritical
Google Play Data Safety form completed accurately — data types collected and purposes declaredCritical
Only necessary permissions requested — camera, location, contacts requested only when feature needs themCritical
Permission requests include rationale — system permission dialogs explain why permission is neededCritical
App passes certificate pinning or uses secure channel for sensitive API callsHigh
User data can be exported and deleted on request — GDPR data subject rights implementedHigh
App does not collect analytics or crash data without user consent where required by regulationHigh
Jailbreak / root detection considered if app handles financial or sensitive dataHigh
Code obfuscation applied to release builds to prevent reverse engineeringMedium
Screenshot prevention enabled on screens containing sensitive data (payment details, medical records)Medium
9 critical · 4 high · 2 medium
🍎
04
Category

Apple App Store Submission

Apple's review process is thorough and strict. Missing a single required field or violating a guideline can delay your launch by weeks. Complete every item before submitting.

17Items
Apple Developer Program account active ($99/year) with correct team membershipCritical
App bundle identifier (com.yourcompany.appname) registered in App Store ConnectCritical
Distribution certificate and provisioning profile created and correctly configuredCritical
App built with the latest Xcode release targeting the current iOS SDKCritical
App icon provided at 1024×1024px (PNG, no alpha channel) in App Store ConnectCritical
Screenshots provided for all required device sizes: 6.9" iPhone (required), 6.5", 5.5", and iPad if universalCritical
App name (30 chars max), subtitle (30 chars max), and description written and proof-readCritical
Keywords field optimised (100 chars max) with high-value, non-brand search termsCritical
Privacy Policy URL entered in App Store Connect — must be publicly accessibleCritical
Age rating questionnaire completed accurately — incorrect rating causes rejectionCritical
In-app purchases configured and reviewed in App Store Connect if app is monetisedCritical
TestFlight beta testing completed with at least 10 external testers before App Store submissionCritical
App preview video created (15–30 seconds, device-captured footage, no marketing text or music)High
Review notes provided if app has login requirements — provide demo account credentialsHigh
App category and subcategory selected appropriately for discoverabilityHigh
Support URL and marketing URL entered — must be live and working at time of reviewMedium
Version notes (What's New) written for the first releaseMedium
12 critical · 3 high · 2 medium
🤖
05
Category

Google Play Store Submission

Google Play has different requirements to Apple. The Android App Bundle (AAB) format, content rating, and data safety form are the most commonly missed items.

16Items
Google Play Developer account active ($25 one-time fee) and payment profile set upCritical
App signed with upload keystore — keystore file backed up securely (loss means new app listing)Critical
App built as Android App Bundle (AAB) not APK — AAB required for new apps since August 2021Critical
Target SDK version is current (minimum API 34 / Android 14 as required by Google Play policies)Critical
App icon uploaded at 512×512px (PNG, 32-bit with alpha) for Google Play listingCritical
Feature graphic uploaded at 1024×500px — displays at top of listing and in Google Play editorialCritical
Minimum 2 screenshots uploaded (up to 8) — at least one phone size, plus tablet if app supports itCritical
Short description (80 chars) and full description (4000 chars) written and optimised for ASOCritical
Content rating questionnaire completed via IARC — rating certificates auto-generatedCritical
Data Safety section completed accurately — lists all data types collected and their purposesCritical
App access instructions provided if app requires login — reviewer credentials for any paywalled contentCritical
Internal testing → Closed testing → Open testing track completed before production rolloutHigh
App category and tags selected — affects discoverability in Play Store search and browseHigh
Phone and tablet screenshots provided separately if app has a distinct tablet layoutHigh
Promotional video linked (YouTube URL) — shown on listing and in editorial featuresMedium
Google Play Instant configured if short trial experience is viable for your appMedium
11 critical · 3 high · 2 medium
🔍
06
Category

App Store Optimisation (ASO)

ASO is the App Store equivalent of SEO. An optimised listing converts more viewers into downloads and ranks higher for relevant search terms — before you spend a single dollar on paid acquisition.

14Items
App title contains the primary keyword users search to find your type of appCritical
iOS subtitle (30 chars) contains secondary keywords not in the titleCritical
iOS keywords field (100 chars) contains high-volume, relevant search terms — no spaces, comma-separatedCritical
Screenshots tell a story — first screenshot clearly communicates the core value propositionCritical
Screenshot captions are concise benefit statements — not feature namesCritical
Competitor keyword research done — identify terms competitors rank for that you should targetHigh
Short description on Google Play (80 chars) contains primary keyword in first sentenceHigh
Full description on Google Play leads with the strongest benefit, not the product nameHigh
App preview video showcases the core experience in the first 3 seconds — most users only watch brieflyHigh
Icon A/B tested in Google Play experiments before finalising — different colours, icons, and textHigh
Localised store listings created for top non-English markets if app supports multiple languagesHigh
Keyword ranking tracked for target terms using AppFollow, AppTweak, or Sensor TowerMedium
Competitor listing analysed — understand their screenshots, descriptions, and keyword strategyMedium
In-app events (iOS) or promotional content (Android) planned for post-launch to boost discoverabilityMedium
5 critical · 6 high · 3 medium
👋
07
Category

Onboarding & First-Time User Experience

The first session determines whether a user stays or deletes your app. Most app churn happens within the first 3 days. Onboarding must deliver value before asking for anything.

13Items
New user can reach the core value of the app within 60 seconds of first opening itCritical
Onboarding does not ask for account creation before showing value — show value first, gate laterCritical
Permission requests deferred until the feature that needs them is used — never on first openCritical
Sign-up flow is minimal — only required fields, social login options (Apple, Google) availableCritical
Welcome / tutorial screens are optional or skippable — power users hate forced onboardingCritical
Push notification permission requested only after user has experienced value — not on first launchHigh
Progress saved automatically during onboarding — app resume after interruption works correctlyHigh
Onboarding completion rate measured — drop-off points identified and improved before launchHigh
Social login (Sign in with Apple required if any social login on iOS) implemented and testedHigh
Guest / anonymous mode available if app can provide partial value without accountHigh
Personalisation steps during onboarding are optional and clearly skippableMedium
First-time user experience tested with people who have never seen the app beforeMedium
Onboarding analytics tracked — measure completion rate, time in each step, and drop-off pointsMedium
5 critical · 5 high · 3 medium
💳
08
Category

Monetisation & Billing

In-app purchase and subscription bugs are catastrophic — they either fail silently (losing revenue) or charge users incorrectly (triggering chargebacks and refund requests). Test every billing flow thoroughly.

13Items
In-app purchase products configured in App Store Connect and Google Play ConsoleCritical
Subscription purchases tested with sandbox / test accounts on both platformsCritical
Purchase restoration tested — 'Restore Purchases' works correctly for iOS paid and subscription appsCritical
Subscription state handled correctly — expiry, renewal, cancellation, and billing retry all testedCritical
Entitlements updated in real time — premium features unlock immediately after purchaseCritical
Server-side receipt validation implemented — client-side validation alone is easily spoofedCritical
Free trial correctly converts to paid after trial period — grace period and expiry communicated to userHigh
Subscription management screen accessible from within app — users can cancel without contacting supportHigh
Billing error state handled — user shown clear message if payment fails with guidance on how to fixHigh
Purchase confirmation screen shown after successful transaction with clear summaryHigh
Offer codes / promo codes tested if marketing strategy includes promotional pricingHigh
Revenue Cat or similar subscription management SDK integrated to simplify cross-platform billingMedium
App Tracking Transparency (ATT) prompt configured if using IDFA for advertising attribution on iOSMedium
6 critical · 5 high · 2 medium
📊
09
Category

Analytics, Crash Reporting & Monitoring

You cannot improve what you cannot measure. Set up analytics and crash reporting before launch — your very first user session should be captured and your first crash should alert you within minutes.

13Items
Crash reporting SDK integrated and live (Firebase Crashlytics or Sentry) — verified by triggering a test crashCritical
Crash reporting alert configured — you are notified within 10 minutes of any crash occurringCritical
Analytics platform integrated (Firebase Analytics, Mixpanel, or Amplitude)Critical
Key events tracked: app_open, sign_up, onboarding_complete, core_action, purchase, churnCritical
Retention cohorts configured — Day 1, Day 7, and Day 30 retention visible from first userCritical
Funnel analysis set up for onboarding and core conversion flowsHigh
App Store Connect analytics enabled — downloads, impressions, conversion rate, and retention visibleHigh
Google Play Console statistics configured — install sources, ratings, and ANR rates trackedHigh
Performance monitoring enabled (Firebase Performance) — network request latency and app startup time trackedHigh
User property tracking configured — plan tier, platform, app version tracked against eventsHigh
Session recording or heatmap tool integrated (UXCam or FullStory) for first 30 days post-launchMedium
Revenue tracking connected — in-app purchase events linked to analytics for LTV analysisMedium
Attribution SDK integrated (AppsFlyer or Adjust) if running paid acquisition campaignsMedium
5 critical · 5 high · 3 medium
⚖️
10
Category

Support, Legal & Compliance

Both Apple and Google require Privacy Policies and Terms of Service. Missing legal documentation or failing to handle regulated data correctly leads to review rejection and potential legal liability.

13Items
Privacy Policy published at a public URL and linked in the app store listingCritical
Terms of Service / EULA accessible within the app and linked from the store listingCritical
In-app support channel available — at minimum an email address or in-app chatCritical
Account deletion flow implemented within the app — Apple requires in-app account deletion since June 2022Critical
GDPR compliance implemented — EU users can access, export, and delete their dataCritical
COPPA compliance verified — app not collecting data from children under 13 without parental consentCritical
App content rating is accurate — incorrect ratings (especially 4+ vs 12+) cause rejectionHigh
App does not contain prohibited content per App Store Review Guidelines or Google Play PoliciesHigh
User-generated content moderation system in place if app allows UGCHigh
Support email monitored — App Store and Play Store reviewers may contact the support emailHigh
App version and build number incremented correctly — cannot submit the same build number twiceHigh
CCPA opt-out mechanism for California users if app collects data for advertisingMedium
Status page or in-app message system for communicating outages to usersMedium
6 critical · 5 high · 2 medium
🚀
11
Category

Post-Launch & Growth

Launch day is the beginning, not the end. The first 30 days determine whether your app grows organically or stalls. These steps maximise your launch momentum.

12Items
Launch day monitoring plan in place — team available to respond to critical bugs and reviewsCritical
Response to every App Store and Play Store review in first 2 weeks — especially negative onesCritical
Crash rate monitored hourly on launch day — hotfix release plan ready to deploy within 4 hoursCritical
App Store review prompt configured — triggered at the right moment (after first positive interaction)High
Push notification strategy defined — day 1, day 3, and day 7 re-engagement messages plannedHigh
Product Hunt, Hacker News, and relevant community launch posts drafted and scheduledHigh
User interview plan active — schedule 5 calls with early users in first weekHigh
Referral or invite mechanism in place to encourage word-of-mouth growth from early adoptersHigh
Phased rollout strategy — release to 10% then 50% then 100% on Android to catch issues earlyHigh
App store listing A/B test set up in Google Play experiments for icon, screenshots, and descriptionMedium
Featured app submission to Apple and Google editorial teams if app quality warrants considerationMedium
Update cadence defined — commitment to regular updates signals active development to users and storesMedium
3 critical · 6 high · 3 medium
Built by 4Byte

How 4Byte launches mobile apps

This checklist is built from our direct experience submitting and launching iOS and Android apps for 45+ clients. We have seen every rejection reason, every billing bug, and every launch-day incident that this checklist is designed to prevent.

We build cross-platform apps in Flutter and React Native — delivering a production-ready iOS and Android app simultaneously in 28 days, with App Store and Google Play submission handled as part of every engagement.

App Store and Google Play submission included in every mobile build
Crash reporting, analytics, and ASO set up before launch day
TestFlight and Play testing track completed before public release
Post-launch monitoring and first-update support included
45+

Apps Shipped

iOS + Android simultaneously

28 days

App Delivery

Kickoff to App Store live

Both

Stores Handled

App Store + Google Play

≤ 4hrs

Response Time

On all new enquiries

FAQ

Frequently Asked Questions

How long does it take to get an app approved on the App Store?+

Apple App Store reviews typically take 1 to 3 business days for new app submissions. Expedited reviews are available for critical bug fixes. Rejections can add 1 to 2 weeks if a resubmission is required. Plan for a minimum of 2 weeks between submission and public availability, especially for your first submission which faces more thorough review.

How long does Google Play app review take?+

Google Play reviews typically take 1 to 3 days for new apps, though some reviews take up to 7 days. Google uses automated checks plus human review for policy compliance. New developer accounts face longer review times as part of the verification process. Plan for at least 1 week between submission and public availability.

What is ASO and why does it matter for app launch?+

App Store Optimisation (ASO) is the process of optimising your app's listing to rank higher in App Store and Google Play search results. It covers app title, subtitle, keywords, description, screenshots, and preview video. ASO can increase organic downloads by 30 to 50 percent compared to an unoptimised listing. It is the most cost-effective acquisition channel for mobile apps.

What app permissions should I request at launch?+

Request only the permissions your app genuinely needs to function. Request permissions contextually — at the moment the feature that requires them is used, not on first launch. Common mistakes include requesting location, camera, and notification permissions before the user understands why. Each unnecessary permission request reduces trust and increases the chance the user denies or deletes the app.

What metrics should I track after launching a mobile app?+

After launching a mobile app, track daily active users (DAU) and monthly active users (MAU), Day 1, Day 7, and Day 30 retention rates, session length and frequency, crash rate (target under 0.1 percent), App Store and Google Play ratings, revenue metrics (if monetised), and user acquisition cost versus lifetime value. Retention is the most important signal of product-market fit for mobile apps.

How many screenshots do I need for App Store and Google Play?+

Apple App Store requires at least one screenshot per device size and supports up to 10 screenshots per device. You must provide screenshots for iPhone and can optionally add iPad. Google Play requires at least 2 screenshots and supports up to 8 per device type. Both platforms support a preview video which significantly increases conversion rate on the listing page.

Related Resources

More Templates & Guides

ChecklistSaaS Launch ChecklistView resource →ChecklistTechnical SEO ChecklistView resource →ComparisonFlutter vs React NativeView resource →TemplateMVP Planning TemplateView resource →
Open for new projects

Ready to launch your mobile app?

We build and launch cross-platform iOS and Android apps in 28 days — including App Store submission, crash reporting, ASO, and every item on this checklist. Free strategy call, response in under 4 hours.

Book a Free Strategy Call →View Mobile Development →
📞100% Free Strategy Call
Response in ≤ 4 Hours
🛡️No Obligation
🚀45+ Products Shipped