- Home
- App launch checklist
App launch checklist
App launch checklist: from store listing to the first week of reviews
Launching an app means launching two pages at once: the store listing and the website that sends people to it. Both have to be ready, and they have to tell the same story. This checklist covers mobile apps and web apps, from the weeks before launch to the first week after.
Where our scanner checks the website side, you will see how the 58 app pages we have scored actually do.
Data updated November 4, 2026 from 241 scans
1. Positioning: one sentence, one audience
Write the sentence that explains the app to a stranger: what it does, who it is for, and why it is better than what they use now. That sentence becomes the store subtitle, the landing page headline and the first line of every launch post.
- One-sentence description written and tested on a stranger
- One primary audience chosen for launch
- Same name and description ready for store and website
How launch pages score on this item (Clear headline (H1)): missing on 35% of 57 app pages (web or mobile apps, by the scan's site type or category) we scanned. It was missing on 5% of pages scoring 70 or more and 68% of pages under 50. Across all scanned pages, those with it averaged 60.3 points out of 100; those without it, 34.4.
2. Store listing (mobile apps)
The store listing is your second landing page. Screenshots are the most important element: most people decide from the first two. Show the app's best moment with real content, with a short caption on each. Check each store's current requirements for sizes, character limits and review guidelines before you submit, and leave time for review.
- App name and subtitle that say what the app does
- First two screenshots show the main value, with captions
- App preview video, if your store supports it
- Description written for people, with keywords used naturally
- Privacy details and data-use labels filled in accurately
- Support URL and privacy policy URL live
- Submitted early enough to allow for review and a rejection
3. Landing page that shows the app
The website is where launch posts, press and search send people. Show the app in a device frame with a real screen, above the fold. Many app pages skip this: in our data, a large share of app pages had no product screenshot the scanner could find. See app landing page examples.
- Real app screen in a device frame above the fold
- Outcome headline that matches the store subtitle
- A short muted loop of the core interaction
How launch pages score on this item (Product screenshots / creative): missing on 53% of 57 app pages (web or mobile apps, by the scan's site type or category) we scanned. It was missing on 7% of pages scoring 70 or more and 83% of pages under 50. Across all scanned pages, those with it averaged 62.6 points out of 100; those without it, 39.7.
4. Download and sign-up paths
Make it easy to get the app from wherever the visitor is. Show official store badges for each platform you support. Give desktop visitors a QR code or a "send me a link" option. For web apps, one clear "Start free" or "Sign up" button. If the app is not out yet, use a waitlist form.
- Official store badges for every supported platform
- Desktop handoff: QR code, or email or text me a link
- Web app: one clear sign-up button
- Pre-launch: waitlist form with one field
How launch pages score on this item (Primary call-to-action): missing on 42% of 57 app pages (web or mobile apps, by the scan's site type or category) we scanned. It was missing on 28% of pages scoring 70 or more and 76% of pages under 50. Across all scanned pages, those with it averaged 60.4 points out of 100; those without it, 42.5.
5. Proof that fits a new app
A new app has no ratings yet. Use what is real: quotes from beta testers (with permission), a note from the founder, press if you have it, or the number of people on the waitlist if it is true. Add store ratings once you have enough to be meaningful. Never post fake reviews in the store or on the page.
- At least one real quote from a beta tester
- Founder or team visible on the website
- A plan to ask happy users for store reviews after launch
How launch pages score on this item (Social proof / testimonials): missing on 56% of 57 app pages (web or mobile apps, by the scan's site type or category) we scanned. It was missing on 5% of pages scoring 70 or more and 85% of pages under 50. Across all scanned pages, those with it averaged 63.2 points out of 100; those without it, 38.3.
6. Share previews and press kit
Launch posts are shared as links. Set Open Graph tags and a share image on the website, and prepare a small press kit: the icon, three to five screenshots, a short description and a contact email. See OG image examples.
- Open Graph title, description and 1200 × 630 image
- Press kit: icon, screenshots, description, contact
- Short demo video ready to post on social
How launch pages score on this item (Social share image (OG)): missing on 23% of 57 app pages (web or mobile apps, by the scan's site type or category) we scanned. It was missing on 12% of pages scoring 70 or more and 53% of pages under 50. Across all scanned pages, those with it averaged 57.4 points out of 100; those without it, 36.
7. Analytics and attribution
Set up analytics in the app and on the website before launch. Track the steps that matter: install, sign-up, onboarding completed, first key action. Use campaign links for each launch channel so you can tell which ones brought people who stayed.
- In-app analytics for install, sign-up, onboarding, first key action
- Website analytics with store-badge click events
- Campaign or UTM links for every launch channel
- Crash reporting enabled
8. Pricing and monetisation
If the app is paid or has in-app purchases, test the full purchase flow in the store's test environment, and state the price clearly on the website. If it is free with paid upgrades, say so in one line.
- Purchase and restore flows tested
- Price or "free with upgrades" stated on the website
- Refund and cancellation path explained
How launch pages score on this item (Pricing or offer): missing on 23% of 57 app pages (web or mobile apps, by the scan's site type or category) we scanned. It was missing on 2% of pages scoring 70 or more and 60% of pages under 50. Across all scanned pages, those with it averaged 58.4 points out of 100; those without it, 35.2.
9. Launch week
Launch on a day you can respond. Post on the two or three channels where your audience is. Watch crash reports, reviews and support messages closely. Reply to every review in the first week, especially the critical ones: other people read the replies.
- Launch posts published on two or three channels
- Crash reports checked daily
- Every store review answered
- Support inbox answered within a day
- A quick fix release ready if needed
10. After launch week
Look at where people drop off between install and the first key action, and fix the biggest drop first. Ask engaged users for a review at a good moment, not on first open. Keep the website updated with new screenshots and real ratings as they arrive.
- Biggest onboarding drop-off identified and a fix scheduled
- In-app review prompt after a success moment
- Website updated with real ratings and current screenshots
How launch pages score on this item (Blog / changelog / updates): missing on 56% of 57 app pages (web or mobile apps, by the scan's site type or category) we scanned. It was missing on 23% of pages scoring 70 or more and 85% of pages under 50. Across all scanned pages, those with it averaged 62.8 points out of 100; those without it, 42.2.
One last check
Before launch posts go out, open your website on a phone, tap the store badge, and make sure it lands on the right listing. Then paste the website URL into a chat to see the preview.
To check the website side automatically, run it through the free landing page analyzer: it scores the page out of 100 and names the biggest gap. For the wider launch, see the product launch checklist, and for Product Hunt specifically the Product Hunt launch checklist.
FAQ
How long before launch should I submit my app for review?
Leave enough time for at least one rejection and resubmission. Review times vary by store and by time of year, so check current guidance from each store and do not schedule launch posts until the app is approved.
Do I need a website if my app is in the App Store?
Yes. Launch posts, press and search send people to a website, not a store listing. The website also needs to host your privacy policy and support page, which the stores require.
Where do the numbers on this page come from?
From 58 app pages (web and mobile) scanned with the free LaunchBuddy scanner, using each site's latest scan. We publish aggregates only, never which sites were scanned.
Check your launch page in a minute
The free analyzer runs the same 13-item launch checklist behind the numbers on this page, scores your page out of 100 and names the one gap to fix first. No account needed.
Numbers are aggregates from launch pages people scanned with LaunchBuddy; we never publish which sites were scanned. Items marked found or missing come from a static read of one page, so content that only appears after JavaScript runs can be missed.