The Gap Between Approval and Downloads
Getting your iOS app approved is a milestone. Getting your first 1000 downloads is a different challenge entirely.
Most indie developers treat the approval email as the finish line. It's actually the starting gun. The work that happens in the 48 hours before and after your app goes live has an outsized effect on your first-week performance — which in turn affects your App Store ranking, your review count, and your early growth trajectory.
This checklist covers everything you need to do, in order, to give your app the best possible start.
---
Before You Submit: Pre-Launch Prep
These tasks should be completed before your app goes into review.
✅ Optimize Your App Store Listing
Your App Store listing is your primary marketing asset. Before submitting:
- Title: Include your primary keyword naturally. The title has the highest weight in App Store search.
- Subtitle: 30 characters to add a second keyword or reinforce your value proposition.
- Keywords field: 100 characters, comma-separated, no spaces after commas. Use keywords not already in your title or subtitle.
- Description: The first three lines appear above "more" — make them count. Lead with the benefit, not the feature.
- Promotional text: This can be changed without a new submission. Use it for time-sensitive messaging ("Now with iOS 18 widgets!").
✅ Create Professional Screenshots
Your screenshots are the most important visual element of your listing. Users decide whether to download in seconds, and screenshots are what they look at.
Follow the App Store screenshot size requirements for each device type you support. Beyond the raw screenshots, create styled showcase images — screenshots in device frames with background colors and caption text — for your social media launch posts.
AppFrame generates these showcase images automatically from your App Store screenshots. They're useful both for your launch posts and for your press kit.
✅ Set Up Your Landing Page
Even a minimal landing page — one page with your app name, icon, screenshots, and an App Store link — gives you something to link to from social profiles and email campaigns. It also establishes your web presence before anyone is searching for your app by name.
✅ Build Your Email List
If you've been building in public or have any existing audience, collect emails before launch. A pre-launch list of even 50–100 people who asked to be notified gives you a built-in audience for launch day.
✅ Draft Your Launch Posts
Write your launch posts before your app is approved. You want to publish immediately when you go live, not spend two hours writing copy while momentum is slipping.
Draft posts for: - Twitter/X (a thread) - LinkedIn - Reddit (relevant communities) - Any Slack groups or Discord servers you're part of
✅ Prepare Your Press Kit
If you're reaching out to journalists or bloggers, have your press kit ready before launch. It should include your app icon, screenshots, showcase images, a short description, and your contact information.
---
Launch Day: The First 24 Hours
✅ Post Your Launch Announcement
Publish your prepared posts across all channels. Do this the moment your app appears as "Ready for Sale" — not when you get the approval email, which can precede App Store availability by up to an hour.
Sequence your posts: 1. Twitter/X first (most real-time, fastest feedback) 2. LinkedIn within the hour 3. Reddit (pick the right community — not r/self-promotion) 4. Email your list 5. Notify your personal network
✅ Submit to Product Hunt
If you've prepared a Product Hunt launch (which is recommended), publish it the moment your app is live. Product Hunt launches are evaluated over a 24-hour period, so timing matters — publish at 12:01 AM Pacific time to get the full day.
If you haven't prepared a full Product Hunt launch, schedule it for a future day rather than rushing it.
✅ Post in Relevant Communities
Beyond developer communities, post in communities your target users belong to. If it's a fitness app, post in fitness subreddits. If it's a writing tool, post in writing communities. Lead with the problem you solved, not with "check out my app."
✅ Message Your Early Supporters
Personally message people who expressed interest during development. These are your warmest leads and most likely to leave early reviews.
✅ Monitor Reviews
Check for reviews throughout the day. Respond to every review — positive and negative. Early review responses show the App Store algorithm (and potential users) that you're actively maintaining the app.
---
First Week: Building Momentum
✅ Respond to Every Review
Make it a daily habit in week one. Responding to negative reviews often leads to updated ratings. Responding to positive reviews builds goodwill.
✅ Submit to App Discovery Sites
There are several sites that list new iOS apps. Submitting takes 15–30 minutes and can generate a small but consistent trickle of downloads:
- AppAdvice — Accepts new app submissions
- AppRaven — Curated app discovery
- Launching Next — App launch directory (not iOS-specific)
- Betalist — If you still have a beta/early access phase
✅ Write a Launch Retrospective
A post about how your launch went — download numbers, what you tried, what worked — is among the most-shared content in the indie developer community. Write it at the end of week one when you have real data.
Post it on Indie Hackers, Medium, and your own blog (if you have one). This content drives ongoing discovery long after your launch day.
✅ Identify Your Best Marketing Channel
After a week, look at your data. Where did your downloads come from? Which post got the most engagement? Which community responded most positively?
Double down on whatever worked. Don't spread effort evenly across every channel — focus on the one or two that showed real signal.
✅ Set Up Analytics
If you haven't already, integrate a lightweight analytics tool. TelemetryDeck is the privacy-respecting option that requires no consent banner. Even just tracking which screens users visit and where they drop off will inform your first update.
---
After Week One: The Path to 1000
Getting from 0 to 1000 downloads typically takes longer than launch week for most indie apps. The realistic timeline depends heavily on your category and marketing, but here's a framework:
100 downloads: Achievable through your personal network and launch posts. This is "friends and interested strangers" territory.
500 downloads: Requires getting into channels you don't personally control — media mentions, App Store feature consideration, review sites, or word of mouth from early users.
1000 downloads: Usually requires either one big placement (a feature, a viral post, press coverage) or sustained, compounding organic growth through App Store search.
The path from 100 to 1000 is where ASO starts to matter most. Update your keywords based on what you learn from App Store Connect analytics. Test different screenshots using Apple's built-in A/B testing. Improve your description based on user feedback.
The launch checklist gets you to 100. The ongoing optimization work gets you to 1000 and beyond.
---
The Mindset Behind the Checklist
Every item on this list has the same goal: reduce friction between your app and the people who would benefit from it.
Your app doesn't automatically find its users. You have to introduce them. The checklist is a structured way to make those introductions as broadly and effectively as possible in the critical window when your app is new and the algorithm is paying attention.
Do the work. Ship the posts. Respond to the reviews. The downloads follow from the effort.