App store launch checklist: what to do before you hit submit

Getting an app approved is the easy part. Getting it ready to succeed the moment it's live is the part founders skip.

There are two ways a launch goes wrong. The obvious one is rejection — Apple or Google bounces your submission over something you could have fixed in advance. The quieter, more expensive one is launching into silence — the app goes live, technically fine, and no one finds it or stays. Both are preventable with preparation. Here's the checklist.

The submission essentials (avoid rejection)

These are the things that get builds bounced at review. Handle them before you submit:

• Privacy policy and data disclosures. Both stores require a privacy policy plus accurate data-disclosure summaries — Apple's privacy labels and Google Play's Data Safety section — that match what your app actually does. Inaccurate labels are a common rejection cause.
• Permissions with justification. Every permission you request needs a genuine, explained reason. Unexplained or excessive permission requests get flagged.
• Accurate metadata. Your description, screenshots, and category must reflect the actual app. Misleading listings get rejected.
• Age rating and category rules. Set an accurate age rating, and confirm any category-specific requirements (kids, health, finance) are met.
• No obvious bugs or crashes. Reviewers do use the app. A build that crashes on a core flow gets bounced.

Most of this traces back to the compliance checklist, which is far cheaper to handle during planning than to discover at the review gate, where a rejection can cost a week.

The discovery essentials (avoid silence)

Passing review gets you listed. It doesn't get you found. Before launch, prepare the things that determine whether anyone discovers and installs:

• App store optimization. Your title, subtitle, keywords, icon, and screenshots drive both ranking and conversion. This is your primary discovery channel and it's set at submission — see ASO basics.
• Screenshots that sell. Most install decisions happen on the screenshots. Lead with your strongest value and use captions to communicate benefits, not just show raw UI.
• A launch plan. Where will the first users come from? A finished app with no user-acquisition plan is the classic launch into silence.

The measurement essentials (so you can learn)

Launch is the start of learning, not the end of building — but only if you can see what's happening. Confirm before you ship:

• Analytics installed and verified. Confirm your tracking actually fires on the live app, not just in theory. Retrofitting analytics after launch permanently loses your earliest, most valuable data.
• Key events tracked. Activation steps, the core loop, and conversion moments, per your event-tracking plan.
• Crash and performance monitoring. So a launch-day problem surfaces immediately instead of through angry reviews.

The retention essentials (so users stay)

Winning an install is expensive; keeping the user is where the value is. The first-run experience has to be ready on day one:

• Onboarding that reaches first value fast — see onboarding best practices. A broken first session churns users no matter how good the idea.
• A re-engagement plan — lifecycle messaging and push, set up with restraint, ready to bring users back.

Why the checklist is really a planning artifact

Read back through it and the pattern is clear: almost none of this is last-minute work. Privacy, ASO, analytics, onboarding, a launch plan — these are decisions and preparations that belong in your plan, not your final week. Teams that treat launch as a checklist to rush through at the end hit rejections and silence. Teams that planned these from the start just execute. That's the whole argument for preparing before you build, laid out in launching an app and keeping users and planning your app.