Hitting Publish is not a launch. It's the moment your app becomes findable, which matters only if anyone is looking. A real mobile app launch is a four-week sequence, and most of it happens before and after the day itself.
This checklist is the sequence. It assumes you're an indie developer or a small team, it covers both the App Store and Google Play, and every item on it is free. Work through it phase by phase and you'll launch with a listing that ranks, testers who've already caught the embarrassing bugs, and somewhere to send people besides your mom.
Four weeks out: get the listing right
Your store listing does more for your launch than anything you'll post on launch day, because it keeps working after the launch-day traffic goes home. Roughly 60% of installs start with a store search. The listing is the launch.
- Pick your keywords first. Before you write a word of store copy, decide which 5–10 search terms you deserve to rank for. Look for terms that describe the problem, not just the category: "sleep sounds for babies" beats "sleep app" for a new developer. The app store keyword research guide walks through the full method.
- Write the title and subtitle around those keywords. You get 30 characters for the title on both stores, a 30-character subtitle on iOS, and an 80-character short description on Google Play. Your strongest keyword belongs in the title; the next two go in the subtitle or short description.
- Write the description for the store you're on. Google Play indexes your description for search; Apple doesn't. So the Play version carries your keywords naturally, and the iOS version sells. If writing store copy makes you procrastinate, the free App Store listing generator and Google Play listing generator produce a draft inside the exact character limits, and you edit from there.
- Finish screenshots now, not launch week. The first two screenshots decide the install for most people. Get the exact screenshot sizes right the first time so you're not re-exporting at midnight, and put your single biggest benefit in screenshot one.
- Score the draft before Apple and Google see it. Run your listing through the free App Store ASO checker or Google Play ASO checker. Fixing a weak subtitle takes two minutes in a draft and a full review cycle after submission.
Two weeks out: test, warm up, line things up
- Ship to real testers. TestFlight on iOS; a closed test track on Google Play. You're not just hunting crashes: watch where testers hesitate, because that hesitation shows up later as one-star "confusing" reviews.
- Handle Google's testing requirement early. If you created a personal Play Console account after November 13, 2023, Google requires a closed test with at least 12 testers opted in for 14 continuous days before you can apply for production. Those 14 days are a hard floor, so start the clock now. It's the single most common thing that silently pushes an Android app launch back a month.
- Warm up the accounts you'll launch with. A fresh Reddit account posting a launch link gets removed by automod before a human sees it. The Reddit account warm-up guide covers the two-week fix. The same logic applies on X: an account that only ever posts its own link performs like one.
- Collect your launch list. Directories, subreddits, Discord and Slack communities, newsletters that cover your niche, and the handful of people who said "tell me when it's out." Write them all down with the date you'll hit each. Launch week is a terrible time to be doing research.
- Prepare an App Store promo and a press-style blurb. One paragraph, one screenshot set, one link. Anyone who offers to share your app should get something they can paste in 30 seconds.
Launch week: spread it out
The biggest launch-week mistake is firing everything on Monday morning and spending the rest of the week refreshing a dashboard. Attention decays in hours; spreading pushes across five days keeps a steady stream of new eyes on the listing, and steady installs look better to store algorithms than one spike followed by silence.
- Day one: your owned channels. Your list from two weeks ago, your X account, your newsletter if you have one. Ask for honest feedback, not upvotes.
- Day two: directories. Submit to the app directories and startup listing sites relevant to your niche. Each one is small alone; together they're your first backlinks and a trickle of high-intent visitors.
- Day three: Product Hunt, if it fits. Best for tools, productivity, and developer-facing apps. Reply to every single comment. A maker who answers everything outperforms a better product that goes quiet.
- Day four: the communities you warmed up. Post where people already discuss the problem you solve, and write the post about the problem, not the app. The Reddit marketing guide covers the format that doesn't get removed.
- Day five: the people already asking. Search Reddit and X for people describing your exact problem this week and reply to them directly. This is the highest-conversion channel on this list, and it's the one ReachFront's Growth Engine automates: it finds those threads for you daily, so start free at ReachFront and let it run through launch week.
All week: reply to everything within the hour when you can. Early comment sections decide what the next hundred readers think.
The week after: convert the spike
Launch day installs are borrowed attention. The week after decides whether you keep any of it.
- Respond to every review, fast. Within 24–48 hours. Users who get a real reply frequently raise their rating, and both stores treat review responsiveness as a signal of an app that's alive.
- Check what actually ranked. Look up where you stand for each of your target keywords. If you're on page one for anything, that term earned more of your title and subtitle. If you're invisible everywhere, your keywords were too ambitious: pick narrower ones and resubmit metadata.
- Fix the top complaint and ship. One visible update within two weeks tells early users they bet on the right developer, and tells the algorithm this app is maintained.
- Keep one channel running. Pick the launch-week channel that brought the best users and keep working it weekly. Launches end; distribution shouldn't. The no-budget marketing playbook is the menu.
The one-screen version
Four weeks out: keywords chosen, title and description written, screenshots done, listing scored. Two weeks out: testers in, Google's 12-tester clock running, accounts warmed, launch list written. Launch week: owned channels, directories, Product Hunt, communities, direct replies, one per day. Week after: answer reviews, check rankings, fix the top complaint, ship an update.
Print that paragraph. It's the whole launch.
Frequently asked questions
How long does it take to launch an app?
Give yourself four weeks from feature-complete to launch day. The store listing, testing requirements, and account warm-up each take one to two weeks, and they overlap. Rushing the sequence usually costs more time than it saves, because Google's 14-day closed-testing window for new personal accounts can't be compressed.
What is the Google Play 12 testers requirement?
Developers who created a personal Play Console account after November 13, 2023 must run a closed test with at least 12 testers opted in for 14 continuous days before they can apply for production access. Plan those two weeks into your launch timeline, and use them to collect real feedback rather than treating the test as a formality.
What's the best day to launch an app?
Tuesday through Thursday gets you the most active audiences on Product Hunt, Reddit, and X, while weekends have less traffic but also less competition. The honest answer: the day matters far less than having your listing, reviews plan, and reply time sorted. A Tuesday launch with a weak listing loses to a Saturday launch with a strong one.
Do I need Product Hunt to launch an app?
No. Product Hunt helps most with developer tools and productivity apps, and a front-page day brings a spike, not a user base. Store search brings most long-term installs, so a listing that ranks beats a launch-day badge. Treat Product Hunt as one push among several, not the launch itself.
What should I do the week after launch?
Respond to every review within 24–48 hours, track your keyword rankings so you know what stuck, fix the most common complaint, and ship a visible update within two weeks. Both stores reward apps that look actively maintained, and early reviewers who get a reply often revise their ratings upward.
Next steps
Start with the part that outlives launch week: score your draft listing free, fix what it flags, then work through how to promote your app so launch day has somewhere to point. If you're pre-launch enough that the idea itself is still soft, validate it first: the cheapest launch mistake to fix is the one you catch before building.