The App Launch Checklist

Shipping an app is mostly code — until the last week, when you discover the long list of accounts, assets, forms and policies both stores expect. This checklist puts all of it in one place, in the order you'll need it. Bookmark it and tick things off as you go.

1. Accounts (start early)

• ☐ Apple Developer Program membership (paid yearly). Organization accounts need a D-U-N-S number, which can take days to get.
• ☐ Google Play Console account (one-time fee) with identity verification completed.
• ☐ New personal Google account? Budget at least two weeks for the mandatory closed test with 12 testers (details in our Google Play requirements guide).
• ☐ Selling in the EU? Apple requires a verified trader status declaration for distribution in the EU.
• ☐ Paid apps or in-app purchases: sign the paid apps agreement, and add banking and tax details in both consoles.

2. Build and technical requirements

• ☐ iOS: built with Xcode 26 or later and the iOS 26 SDK (required for uploads since April 28, 2026), with a minimum deployment target of iOS 13 or later.
• ☐ Android: targetSdkVersion 36 for new apps and updates from August 31, 2026, uploaded as an Android App Bundle (.aab).
• ☐ Unique bundle ID / application ID — you can't change it after publishing.
• ☐ Version number and build number set, and increased for every upload.
• ☐ Release build tested on a real device, with debug logging and test endpoints removed.
• ☐ Privacy manifests included for your app and up-to-date SDK versions (iOS).

3. Icons and launch screens

• ☐ iOS app icon: 1024×1024, opaque, unrounded — plus optional dark and tinted versions. See iOS app icon sizes.
• ☐ Android adaptive icon with background, foreground and monochrome layers, logo inside the 66 dp safe zone. See Android app icon guide.
• ☐ Google Play icon: 512×512 PNG, under 1 MB.
• ☐ Icon tested on light, dark and busy wallpapers at small sizes — try the app icon tester.
• ☐ Launch screen / splash screen matching your first screen. The splash screen generator covers iOS, Android 12+ and Capacitor.
• ☐ All icon files generated in one go with the app icon generator.

4. Store listing text

• ☐ Name, subtitle and keywords researched — use the words your users actually search for.
• ☐ Description that leads with the benefit in the first two lines (that's what shows before "more").
• ☐ Support URL (App Store, required) and contact email.
• ☐ Category and, for Google Play, tags chosen.
• ☐ No "#1", "best", prices or competitor names in the title or graphics.

5. Screenshots and graphics

• ☐ iPhone screenshots at 6.9-inch (e.g. 1320×2868) — 1 to 10. See App Store screenshot sizes.
• ☐ iPad screenshots at 13-inch (2064×2752) if you support iPad.
• ☐ Google Play screenshots: 2 to 8 per device type; four or more at 1080×1920+ for better placement.
• ☐ Google Play feature graphic 1024×500, JPEG or 24-bit PNG — make it with the feature graphic maker.
• ☐ Captions on screenshots, created with the screenshot maker.
• ☐ Optional: app preview video (App Store) / YouTube promo video (Google Play).

6. Privacy and legal

• ☐ Privacy policy at a public URL, linked in both consoles and inside the app. Generate one with the privacy policy generator, and read what to include.
• ☐ Apple App Privacy details completed and consistent with the policy.
• ☐ Google Data safety form completed and consistent with the policy.
• ☐ Account deletion in the app (and a web deletion link for Google Play) if you have accounts.
• ☐ App Tracking Transparency prompt if you or an SDK track users (iOS).
• ☐ Consent message for personalized ads in the EU/UK if you show ads.
• ☐ Age rating questionnaires answered (Apple's updated 2026 age rating questions and Google's IARC questionnaire).
• ☐ Rights to every image, font, sound and piece of music you use.

7. Testing and review

• ☐ TestFlight build tested by a few people outside your team.
• ☐ Google Play closed or internal test run (mandatory 12 testers × 14 days for new personal accounts).
• ☐ Demo account and notes for reviewers if any feature needs a login.
• ☐ All links in the app work, and no placeholder content or "coming soon" screens remain — both are common rejection reasons.
• ☐ In-app purchases submitted for review together with the app version.

8. Launch day and after

• ☐ Choose manual release so you control the exact launch moment after approval.
• ☐ Landing page live, with store badges, a favicon and a download QR code for print and slides.
• ☐ Crash reporting and analytics checked on day one.
• ☐ Reply to early reviews — both stores let you respond publicly.
• ☐ Plan your first update: fixes from real users, plus refreshed screenshots once you see which features people use.

Requirements summarized from Apple Developer "Upcoming requirements", App Store Connect Help, Play Console Help and Google Play Developer Policy. Last checked October 2026.