App Marketing
App Launch Checklist
In short
An app launch checklist covers three phases: the weeks before, when the store listing and audience are prepared; launch day itself, run as a sequence rather than a broadcast; and the week after, when retention tells you whether any of it worked.
Most launches fail on preparation, not execution. You get one first impression per audience and no way to take it back, so the order matters more than the effort.
This is the app launch checklist we actually work through, split into the three phases that matter: the weeks before, the day itself, and the week after — the one nearly everybody skips.
Two to Four Weeks Before Launch
The unglamorous half. Almost every avoidable launch failure traces back to something in this list.
Write the One Sentence
What it does, who for, specific enough that a stranger can repeat it. Everything downstream is built on it — the store listing, the directory blurb, the launch post.
The test: say it to somebody outside your market and ask them to repeat it a minute later. If they can't, it isn't ready.
Build the Store Listing Properly
The first two screenshots and the first line of the description do almost all the work. Most people decide there and never scroll.
| Element | Why it matters |
|---|---|
| Title | Carries the most weight in app store search |
| Subtitle | Second most, and the most commonly wasted field |
| First 2 screenshots | The only thing most visitors look at |
| First line of description | The rest is collapsed behind "more" |
| Icon | The one asset shown everywhere, at 60px |
Get the Keywords Right
The title and subtitle carry the most weight in app store search, which is the whole of app store optimization — ASO for short. Research them; don't guess.
Two rules people break constantly: don't repeat words between title and subtitle, since it wastes the slot, and don't use your category name if you can't realistically rank for it.
Fix Analytics Before Launch, Not After
Install attribution, event tracking and a retention view before the traffic arrives. Launch traffic you can't attribute is wasted twice — once when you can't tell which channel worked, and again when you can't tell which channel to repeat.
Line Up People Who Will Actually Show Up
Twenty people who have agreed beats a thousand followers who haven't been asked. Ask individually, tell them the date, and tell them what you want them to do.
Submit to Review a Week Early
Rejections happen and they aren't fast. A week's buffer costs nothing; a rejection on launch morning costs the launch.
On Launch Day
Pick One Primary Directory
Product Hunt if you've prepared for it; something smaller and less competitive if you haven't. AlphaShot is the low-risk option — a listing there stays up instead of living or dying on one morning, so it doesn't consume your one shot. It's ours, for the avoidance of doubt.
Go Live Early in the Day
Early in the timezone of the audience you want, not yours. Most directories rank partly on same-day momentum, so the first few hours matter more than the rest.
Tell Your List First
Before anything public. They're the people most likely to act, and early activity is what pulls in everyone else.
Be in the Comments All Day
Answering fast is the single biggest difference between launches that place and launches that don't. Block the day out.
Post Where You Already Participate
The communities you've been in for a month, not the ones you joined this morning. The difference is obvious to everyone reading.
The Week After Launch
The phase almost everybody skips, and where most of the value is.
Stagger the Other Directories
One every few days — DevHunt, BetaList, Peerlist, MicroLaunch, TinyLaunch, Uneed, Indie Hackers. Each is a fresh audience and a fresh chance to learn something.
Read and Reply to Every Review
Store rankings weigh reviews, and early ones set the tone for everyone who arrives later. A reply to a bad review is read by the next hundred people.
Watch Retention, Not Installs
Day one and day seven. Installs measure the launch; retention measures the product. If a hundred installs leave four people, the answer isn't more installs.
Ship One Fix
There will be an obvious one. A visible response to early feedback converts more of the remaining traffic than anything else available to you that week.
What Separates a Launch That Works
| Prepared | Unprepared |
|---|---|
| One primary directory, others staggered | Everything submitted the same morning |
| Screenshots built for the listing | Raw screen captures |
| An audience asked in advance | Hope |
| Comments answered within minutes | Checked the next day |
| Analytics installed before launch | Added afterwards, data already lost |
| Retention measured | Installs celebrated |
What Does Launch Support Cost?
If you'd rather not run it yourself, the market ranges look roughly like this. Ours start at £1,600 a month.
| Scope | Typical market range |
|---|---|
| Store listing and creative only | £800–£2,500 one-off |
| Listing plus launch-day coordination | £2,500–£6,000 one-off |
| Ongoing ASO and creative testing | £1,500–£5,000 a month |
Be wary of anyone selling guaranteed rankings or guaranteed installs. Both stores are good at detecting bought activity, and paying for it makes your retention numbers unreadable.
What a Launch Doesn't Do
A launch is a spike, not a channel. It brings a burst of attention, tells you whether the message lands, and produces the first users worth talking to. It doesn't produce sustained growth, and planning the next quarter off launch-day numbers is the most common mistake that follows a good one.
The channels that compound — app store optimization, search, communities, being named in the answers people ask for recommendations — start on launch day and pay much later.
About the author
Sathish · Head of App Marketing
Runs the app side of the practice: store listings, creative testing, and the slow work of getting installs that stay. Reads retention curves before install counts, and says so when a campaign is buying churn.