From Zero to 100 Downloads: The Indie App Launch Playbook That Actually Works

Your app is live. The build is clean, the icon looks sharp, and you've told three friends. Then… nothing. Getting your first 100 downloads is genuinely hard, not because the App Store is broken, but because most developers spend 95% of their time on the product and about 20 minutes on everything else. This playbook fixes that. It's a concrete sequence of actions — not vague advice like 'post on social media' — that any solo developer can execute in the two weeks around launch.

Week Before Launch: Lay the Groundwork

The App Store is a search engine before it's a storefront. Most of your organic downloads will come from people who typed something and found you — so your metadata has to be right before day one, not patched up after. Focus on your app's title, subtitle, and keyword field. Find two or three specific search phrases your ideal user actually types, not broad terms like 'productivity app' but narrower ones like 'habit tracker for students'. Use the 100-character keyword field ruthlessly: no spaces after commas, no repeating words that already appear in your title.

• Write a subtitle that states the clearest benefit, not a tagline — 'Track habits, hit streaks' beats 'Your life, elevated'
• Fill all 100 characters of the keyword field with comma-separated terms, no spaces
• Write your first two lines of the description assuming most people never tap 'more' — that's your real pitch
• Create at least three screenshots that show the UI in context, with a short caption on each one
• Set your primary category and secondary category deliberately — secondary is often ignored and it's free discoverability

If you're launching in more than one language, localise at minimum your title, subtitle, and screenshots for your top two or three target markets. English-only metadata in a Spanish-speaking market is leaving real downloads on the table. Tools like Appolyn can handle the full localisation and publish it in one go, which matters when you're already stretched thin the week before launch.

Launch Day: Create a Small Spike

Apple's algorithm pays attention to velocity — downloads per day relative to your category competition. You won't beat a top-10 app, but you can create a meaningful spike among your real audience that signals relevance. The goal on launch day is to get as many installs as possible from people who actually care, not random traffic.

• Post in one or two niche communities where your target user already hangs out — subreddits, Discord servers, Slack groups, or Facebook groups specific to the problem your app solves
• Write a genuine 'I built this because…' post, not a press release — people respond to the story behind a solo project
• DM up to 20 people you know personally who fit your target user profile and ask for honest feedback, not just a favour
• Submit to directories like Indie Hackers, Product Hunt (pick a Tuesday–Thursday slot), and any newsletter that covers your niche
• Post a short demo video on X/Twitter and any relevant subreddit — video consistently outperforms static screenshots for first impressions

The first 100 downloads are not about scale — they're about finding the people who genuinely needed your app and making sure they can find it back.

Days 2–7: Listen and Iterate Fast

Once you have a trickle of real users, the most valuable thing you can do is watch your reviews and respond quickly. A developer who replies to a one-star review thoughtfully often converts that user into a loyal advocate. More practically, early reviews surface bugs and UX confusion that your beta testers missed. Fix what you can in the first week, ship an update, and mention the fix in your reply to the review — it shows you're active.

• Reply to every review in the first week, even positive ones — it costs two minutes and signals to future users that you're present
• Note every piece of feedback that mentions confusion about the same feature — if three people say it, twenty thought it
• Push a small update within the first 10 days if you can; fresh updates get a minor visibility bump and show momentum
• Check your keyword rankings after five to seven days and swap out any term that isn't ranking in the top 50 — those characters are wasted

Days 8–14: Expand Your Surface Area

Once you've stabilised the core experience, turn your attention to building a few more discovery channels. You don't need all of them — pick two and do them properly.

• Write one genuinely useful blog post or tutorial related to the problem your app solves and post it on Medium, your own site, or a relevant community wiki — this builds organic search traffic over time
• Reach out to two or three micro-influencers or YouTubers in your niche with a free promo code and a one-paragraph pitch — small creators are far more responsive than large ones and their audiences are more targeted
• Set up an Apple Search Ads Basic campaign with a small daily budget — even £2–5 a day can produce measurable installs in a niche category and gives you real conversion data on your product page
• Consider a limited-time price drop or free weekend if you're paid — it generates list activity and can seed reviews

Tracking What's Actually Working

At the end of two weeks you should have real data: which keywords are driving impressions, where your installs are coming from, and what your conversion rate looks like on the product page. If you're using Appolyn, your sales and subscription numbers from App Store Connect are visible alongside your metadata, so you can connect a metadata change directly to a download trend rather than guessing. Without that visibility, it's easy to keep tweaking things that don't move the needle.

One hundred downloads isn't a vanity milestone — it's the point where you have enough signal to know whether your positioning is working, whether your retention is healthy, and whether there's a real audience for what you built. Most apps that fail don't fail because the product was bad; they fail because the developer never found out what was actually stopping people from downloading or staying. Treat the first 100 as a research project, and the next 1,000 becomes a much more informed effort.