App Store Launch Checklist: From Build to Live

Your app is built and tested. Now you need to get it into people's hands. Launching an app on the Apple App Store or Google Play Store is not just uploading a file. There are store listings to prepare, reviews to pass, marketing to coordinate, and a launch-day plan to execute. Miss a step and you could face a rejected submission, a silent launch with no users, or a crash on day one that kills your reputation. This checklist walks you through every step of mobile app development launch from four weeks before to one week after your app goes live. Pair it with our app development timeline so your calendar and your launch checklist stay aligned.

TL;DR

• Start preparing your store listing four weeks before launch. Do not wait until the app is finished.
• Apple reviews take 1 to 3 days. Google takes 1 to 3 hours. Budget extra time for rejections.
• Launch on a Tuesday or Wednesday so you have the full work week to respond to issues.
• The first week after launch is the most important. Monitor crashes, respond to reviews, and watch your analytics.
• After launch, retention work begins. See our app updates retention analytics playbook.

Four weeks before launch: prepare your store listing

Your app's store listing is the first thing potential users see. A good listing convinces them to download. A bad listing makes them scroll past. Start preparing this four weeks before your target launch date. If you are shipping an iOS development build, also review Apple's Human Interface Guidelines and privacy label requirements early so they do not surprise you at submission time.

• Write your app title. Keep it short and include your main keyword. Apple allows 30 characters for the title. Google allows 30 characters for the title and 30 for a short description.
• Write your app description. Explain what the app does and why someone should download it. Lead with the biggest benefit. Apple allows 4,000 characters. Google allows 4,000 characters.
• Create screenshots. You need screenshots for each device size you support. Show the most important features. Add captions that explain each screen. Most successful apps use 5 to 8 screenshots.
• Design your app icon. This is the most visible part of your brand. Keep it simple, recognisable and unique. Test it at small sizes because that is how most people see it.
• Prepare a privacy policy. Both Apple and Google require a privacy policy URL. The policy must explain what data your app collects, why, and how you protect it.
• Set up your developer accounts. Apple Developer Program costs $99 per year. Google Play Developer costs $25 one time. Apply early because Apple approval can take a few days.

For a deeper look at what a full ios app development services engagement covers through store submission, that guide sits alongside this checklist.

Three weeks before launch: beta test

Even if your development team has tested everything, you need real users to test the app before launch. For iOS, use TestFlight to invite testers. For Android, use Google Play's internal testing track. Invite 10 to 20 people: a mix of team members, friends and people from your target audience.

Ask testers to go through every screen, try every feature, and report anything that feels wrong. Pay attention to their feedback about confusion, not just crashes. If three out of ten testers cannot figure out how to complete the main task, your onboarding needs work. Fix the critical issues and test again. An MVP app with a smooth experience beats a feature-rich app with a confusing interface. If you are still shaping that first release, how to build an MVP and our MVP development service page explain how to keep the feature set launch-ready without overbuilding.

Two weeks before launch: submit for review

Submit your app to both stores two weeks before your target launch date. This gives you buffer time for rejections. Whether you used native code or a react native development company stack, the store rules are the same: working flows, honest listings, and accurate privacy disclosures.

Apple App Store submission

Apple reviews every app before it goes live. The review checks that your app follows Apple's Human Interface Guidelines, does not crash, has a working sign-in flow, does not ask for unnecessary permissions, and has accurate screenshots and descriptions. Review typically takes 1 to 3 days. About 20 to 30 percent of first submissions get rejected.

Common rejection reasons include: missing privacy labels (Apple requires you to declare every data type your app collects), broken sign-in (if your app requires a login, you must provide Apple with a demo account), and screenshots that do not match the actual app. If your app is rejected, Apple tells you why. Fix the issue and resubmit. The second review is usually faster.

Google Play Store submission

Google's review is faster, typically 1 to 3 hours for apps from established developers. But Google requires a content rating questionnaire, a data safety form, and compliance with Google Play policies. Google also requires a minimum of 20 testers who have opted in to testing for at least 14 days before you can publish to production. Plan that testing window into your Android development calendar so it does not collide with launch day.

One week before launch: prepare your marketing

The best app in the world fails if nobody knows about it. Plan your launch marketing one week ahead.

• Email your existing audience. If you have an email list, send a launch announcement with a direct link to download.
• Schedule social media posts. Create posts for launch day, day two, and day three. Different content each day: announcement, feature highlight, user testimonial.
• Prepare your website. Add a banner or landing page that links to the app. If you have a blog, publish a post about the launch.
• Set up paid campaigns. If your budget allows, prepare campaigns on Apple Search Ads, Google Ads or Meta. Do not run them yet. Just have them ready to start on launch day.
• Brief your support team. Tell your customer support team about the app. Give them a FAQ document so they can answer common questions from day one.

Document who owns each channel. A silent launch is still one of the most common failures we see when teams treat store approval as the finish line instead of the starting gun.

Launch day: go live

Launch on a Tuesday or Wednesday. This gives you the full work week to respond to issues. Avoid Friday launches because problems over the weekend mean slower response times.

1. Release the app. In App Store Connect, set the release date to today. On Google Play, promote your release from testing to production.
2. Verify the listing. Download the app from the store yourself. Check that the icon, screenshots, description and price are correct.
3. Send your launch communications. Trigger your email, social media posts and paid campaigns.
4. Monitor for crashes. Use a crash reporting tool like Firebase Crashlytics or Sentry. Watch the dashboard closely for the first 24 hours.
5. Watch your analytics. Track installs, sign-ups, first actions and session length from hour one.
6. Respond to reviews. Users who leave reviews on day one are your most engaged audience. Respond to every review, positive or negative.

The first week after launch

The first week determines whether your app gains traction or fades into the background.

Monitor your crash rate. If more than 1 percent of sessions crash, push a hotfix immediately. A high crash rate in the first week tanks your store rating and makes it almost impossible to recover.

Watch where users drop off. If 50 percent of users download but never complete sign-up, your sign-up flow is the problem. If users sign up but never complete the first action, your onboarding is the problem. Fix these issues before adding new features.

Send your first push notification on day 3 or 4. Something useful, like a tip about a feature they have not tried. Users who receive a push notification in the first week are three times more likely to return.

Update your App Store listing based on early data. If a certain screenshot is not getting taps, replace it. If users are searching for your app with a term you did not include in your keywords, add it.

This is also when retention work begins in earnest. Crash fixes and onboarding tweaks in week one feed directly into the longer app updates retention analytics plan you should already have drafted.

Common launch mistakes to avoid

• Launching on Friday. Problems happen over the weekend when your team is slower to respond.
• No monitoring on day one. If your app crashes and you do not know for 8 hours, your first users will never come back.
• Ignoring the store listing. A bad icon, unclear screenshots, or a jargon-filled description costs you downloads. Test your listing before launch.
• Not planning for rejection. Apple rejects 20 to 30 percent of first submissions. Submit early and have a plan for fixes.
• Silent launch. If you do not tell anyone your app is live, nobody will find it. Marketing is not optional.

Launch timeline summary

If you need help with any stage of this process, a development company that handles end-to-end custom software delivery will manage the store submission, launch coordination, and post-launch monitoring for you. You can see how we run that handoff on how we work and in our case studies.

Frequently Asked Questions

How long does App Store review take?

Apple App Store review typically takes 1 to 3 days. Google Play review takes 1 to 3 hours for established developers. Budget extra time for potential rejections.

What percentage of apps get rejected by Apple?

About 20 to 30 percent of first-time submissions get rejected. Common reasons include missing privacy labels, broken sign-in flows, and inaccurate screenshots.

What day should I launch my app?

Launch on Tuesday or Wednesday. This gives you the full work week to respond to bugs, crashes, and user feedback.

How much does it cost to publish an app?

Apple charges $99 per year for a developer account. Google charges a one-time $25 fee. Both take 15 to 30 percent of in-app purchases.

Do I need a privacy policy to publish an app?

Yes. Both Apple and Google require a privacy policy URL that explains what data your app collects and how it is used.

How many screenshots do I need?

Most successful apps use 5 to 8 screenshots. You need screenshots for each device size you support. Captions that explain each screen increase downloads.

What is TestFlight?

TestFlight is Apple's tool for beta testing iOS apps. You invite testers by email, they install the app, and they can report bugs directly through the app.

Should I use paid ads at launch?

If your budget allows, yes. Apple Search Ads and Google App campaigns are effective for launch-week installs. Start with a small budget and scale based on results.

How do I handle negative reviews?

Respond to every review, especially negative ones. Acknowledge the issue, explain what you are doing to fix it, and thank the user for their feedback.

What crash rate is acceptable?

Keep your crash rate below 1 percent of sessions. Above 1 percent, your store rating drops and user trust erodes quickly.

Need help getting your app from build to live? Book a free scoping call. We handle store submission, launch coordination, and post-launch monitoring so you can focus on your business. Start on our mobile app development page.