App Launch Checklist 2026: How to Submit App to App Store & Google Play

Launching an app to the App Store and Google Play involves more than uploading a build and hoping for the best. Both platforms have specific requirements for metadata, screenshots, privacy policies, and technical configurations that must be completed before your app is approved. Missing items lead to rejection and delays. This comprehensive checklist covers everything needed for a successful launch on both platforms in 2026.

TL;DR: App Store submission requires: complete metadata, screenshots, privacy policy URL, privacy nutrition label, app review submission, and 24-48 hour wait. Google Play requires similar items with slight differences. Prepare everything 2-3 weeks before your desired launch date.

Pre-Submission Preparation (2-3 Weeks Before Launch)

Account Setup

Apple Developer Account:

• Active Apple Developer Program membership ($99/year)
• Billing information verified
• Agreements (Paid Applications Agreement) signed in App Store Connect
• Tax forms completed
• Banking information for revenue distribution

Google Play Developer Account:

• Active Google Play Developer account ($25 one-time registration fee)
• Payment profile set up
• Tax forms completed
• Developer profile completed (name, contact info, privacy policy)

App Store (iOS) Submission Checklist

App Store Connect Setup

App Information:

• [ ] App name (30 characters, include primary keyword)
• [ ] Bundle ID matching your Xcode project
• - [ ] SKU (internal identifier, not public)
• [ ] Primary language
• [ ] App category (primary and optional secondary)
• [ ] Content rights statement
• [ ] Age rating questionnaire completed

App Metadata (per version):

• [ ] Subtitle (30 characters, secondary keywords)
• [ ] Description (up to 4,000 characters)
• [ ] Keywords field (100 characters, comma-separated, no spaces)
• [ ] What's New section (for updates)
• [ ] Support URL (must be live and accessible)
• [ ] Marketing URL (optional but recommended)
• [ ] Privacy Policy URL (required for any app with accounts or data collection)

App Store Assets:

• [ ] Screenshots: 6.9" iPhone display (1320×2868 or 1290×2796 px) — up to 10
• [ ] Screenshots: 5.5" iPhone display (1242×2208 px) — required if targeting older devices
• [ ] Screenshots: iPad Pro 13" (2064×2752 px) — if supporting iPad
• [ ] App Preview video: 1080×1920 px, 15-30 seconds, .mov or .mp4 (optional)
• [ ] App icon (1024×1024 px, PNG, no alpha channel)

Privacy and Legal:

• [ ] Privacy Policy URL (live and mobile-accessible)
• [ ] Privacy Nutrition Label completed (data types collected, usage, linked to user)
• [ ] Copyright holder information
• [ ] License Agreement (if applicable, custom EULA)

Pricing:

• [ ] Price tier set
• [ ] Availability by country configured
• [ ] In-App Purchase items configured (if applicable)
• [ ] Subscription groups configured (if applicable)

Build Submission Checklist

Xcode Requirements:

• [ ] App built with latest Xcode version (required for current iOS support)
• [ ] Minimum iOS deployment target set (iOS 16+ recommended in 2026)
• [ ] App icons configured in Asset Catalog (all required sizes)
• [ ] Launch screen configured (no default gray screen)
• [ ] App Transport Security (ATS) configured correctly
• [ ] Privacy usage descriptions included for any accessed permissions:
• Camera: NSCameraUsageDescription
• Microphone: NSMicrophoneUsageDescription
• Location: NSLocationWhenInUseUsageDescription
• Contacts: NSContactsUsageDescription
• Health: NSHealthShareUsageDescription
• Notifications: Handled at runtime

Common Rejection Reasons (2026):

• Missing privacy usage descriptions for accessed permissions
• Crashes on latest iOS or specific devices
• Broken links in app or store listing
• Incomplete or misleading metadata
• Missing privacy policy for apps that collect user data
• Subscription terms not clearly disclosed in app

Google Play (Android) Submission Checklist

Google Play Console Setup

App Setup:

• [ ] App name (50 characters, include primary keyword)
• [ ] Default language
• [ ] App category
• [ ] Tags (up to 5 for discovery)
• [ ] Contact email and website

Store Listing:

• [ ] Short description (80 characters — keyword-important)
• [ ] Full description (up to 4,000 characters)
• [ ] Screenshots: Phone screenshots (minimum 2, recommended 8) — 16:9 or 9:16 ratio
• [ ] Feature graphic: 1024×500 px (required for all apps)
• [ ] App icon: 512×512 px, PNG, 32-bit with alpha
• [ ] Promo video (YouTube URL, optional)

Content Rating:

• [ ] Content rating questionnaire completed (IARC rating system)
• [ ] Appropriate age ratings assigned for all target countries

Privacy:

• [ ] Privacy policy URL (required for apps accessing sensitive data)
• [ ] Data Safety section completed (what data is collected, sharing practices, security)

Target Audience:

• [ ] Target age groups specified
• [ ] Ads in app disclosed (if applicable)

Technical Requirements Checklist

• [ ] APK or Android App Bundle uploaded
• [ ] Minimum API level set (API 26 / Android 8.0 minimum for new apps in 2026)
• [ ] Target API level meets Google's annual requirement (API 35+ in 2026)
• [ ] 64-bit support (required)
• [ ] Permissions justified and minimal (Google reviews unnecessary permissions)
• [ ] All Google Play policies complied with (review policies.google.com/privacy)

Launch Day Execution Checklist

Day Before Launch:

• [ ] App approved and ready in App Store Connect (set publication to "Manual Release")
• [ ] All marketing materials prepared and scheduled
• [ ] Email to waitlist drafted and ready to send
• [ ] Social media posts queued
• [ ] Press release distributed with embargo lift for launch day
• [ ] Support team briefed on expected volume increase

Launch Day (Morning):

• [ ] Release app in App Store Connect (click "Release This Version")
• [ ] Verify app is live in all target app stores
• [ ] Send email to waitlist
• [ ] Post simultaneously across all social channels
• [ ] Submit to ProductHunt (if applicable) — early morning PST
• [ ] Post in relevant Reddit communities

Launch Day (Ongoing):

• [ ] Monitor App Store Connect for crashes or technical issues
• [ ] Respond to first 10+ reviews immediately
• [ ] Check download velocity against targets
• [ ] Monitor social media for user feedback and questions
• [ ] Update any press contacts with launch confirmation

Post-Launch Checklist (Week 1)

• [ ] Analyze onboarding drop-off in Firebase/Mixpanel
• [ ] Review crash reports and fix critical crashes in hotfix
• [ ] Read every initial review and respond
• [ ] Check Day 1 retention baseline
• [ ] Begin push notification strategy
• [ ] Monitor keyword rankings weekly

Frequently Asked Questions

How long does App Store review take in 2026?

Most apps are reviewed within 24-48 hours. Complex apps or first submissions may take up to 7 days. Expedited review is available for critical bug fixes (usually same-day).

Can I schedule my app release for a specific date?

Yes. In App Store Connect, set "Manually Release" to control the exact release moment. This lets you prepare everything, receive approval, then release simultaneously with your marketing campaign.

What happens if my app is rejected?

You receive a detailed rejection reason. Address the specific issue(s) and resubmit. Most rejections are fixable within 1-3 days. For policy disputes, the App Review appeals process is available.

Do I need to update my app immediately after launch?

Plan a 2-week post-launch review period before your first update. This lets you collect real user data on actual issues rather than shipping fixes based on assumptions.

Final Verdict

A successful app launch in 2026 requires completing every item on this checklist before submitting to either store. Missing privacy policy URLs, incomplete metadata, and technical issues are the most common rejection causes — all preventable with proper preparation. Submit 2-3 weeks before your desired launch date to allow for review time and any rejection/resubmission cycles. Visit GetFree.app to discover successfully launched apps and study their App Store listing quality.

Our #1 Checklist Priority: Complete the Privacy Nutrition Label (iOS) and Data Safety section (Android) before submission — these are the most commonly incomplete items that delay approval.

Last updated: February 2026