The moment you tap "Submit for Review" in App Store Connect, the world goes quiet. Your Rork-built app is technically live, the dashboard is open, and the download counter just sits there at zero. Hours pass. Maybe a day. Welcome to the strange post-launch silence that almost every indie developer experiences.
I've shipped multiple apps over the years, and in my experience, the first 100 downloads are harder to earn than the next 10,000. There's no algorithmic tailwind, no reviews, no word-of-mouth. You're starting from absolute zero, and the App Store doesn't owe you any visibility.
This post is a record of the small tactics I've actually used to push through that "calm before nothing" period. Some worked, some didn't. All of them are zero-budget, indie-friendly, and tied to my own launches.
Why the First 100 Downloads Are Uniquely Hard
When a new app appears in the App Store, it gets a tiny amount of "new release" exposure for a few days. If the initial momentum is weak, the app drops out of that feed and effectively vanishes from view.
I went through this exactly with my third app. Technically flawless, but by day three the daily downloads had collapsed to one or two, and it felt like the app was about to be forgotten before anyone had even noticed it existed.
That experience taught me an important lesson. The first 100 downloads aren't earned by marketing after launch — they're set up by preparation before launch. If you start your launch on launch day, you're already late. Most of the work needs to happen one to two weeks earlier.
Pre-Launch: Build Three "Outside Doors" Before You Submit
Before I submit anything to App Store Connect, I make sure my app has at least three doors that don't depend on the App Store itself. Three ways for someone to discover the app from outside.
- A dedicated landing page — Even for a Rork app, I always set up an independent landing page. A static HTML file on Cloudflare Pages or Vercel is plenty. Three or four screenshots, a three-line summary, App Store and Google Play buttons. That's the entire requirement
- Drafted social posts — I write the launch-day posts for X, Instagram, and Threads at least three days in advance. If I try to write them on launch day, they always come out hurried and flat
- Pre-announcements in indie communities — Whether that's Product Hunt's upcoming page, indie hackers, or a Discord channel I'm part of, I post a quiet "launching next week" message a full week before release
The third one matters more than people think. If your first appearance in a community is "Hi, I just shipped this thing," nobody remembers you. But if you say "I'm shipping this next Tuesday" a week earlier, you'll get those crucial first dozens of downloads on day one. That's the only reliable way I know to prevent the dreaded zero-momentum start.
Pre-Launch: Take the Screenshots Seriously
This isn't a tip about technique — it's about mindset. App Store screenshots are the single biggest factor in whether a user decides to download. And yet, in my early launches, I treated them as an afterthought. I'd line up plain Simulator screenshots and call it done. The result: my impression-to-download conversion rate sat below 5%.
Once I started adding a one-line value proposition to each screenshot, cleaning up the background color, and using a device frame, my conversion rate climbed to 10–15%. Same impressions, more than double the downloads.
For a Rork-built app, screenshots have to do extra work. Your app is built with newer tooling that the user has never compared apples-to-apples with. They will judge the app visually, in five seconds, against everything else on their feed. Screenshots are where you earn that judgment.
Launch Day: Time the Announcement for Morning JST
When App Store Connect approves your release, the app goes live in stores around the world in waves. Most indie developers want to announce immediately when the approval email arrives. From experience, this is usually a mistake.
Approval emails tend to arrive in the middle of the night Japan time (during US business hours). If you post then, almost no one in your audience is awake to see it. What I do instead is write the announcement post right after approval, then schedule it for 7–9 a.m. the next morning. That hits the morning commute on X and the morning check-in on Threads. The engagement difference is two to three times larger.
The announcement itself only needs three things: what the app does, why I built it, and where to download it. Long-form copy doesn't get read in feeds. A single screenshot plus a 30-second preview video, on the other hand, measurably increases link clicks.
Week One: Quiet Seeding in Communities
Launch-day social posts aren't enough on their own. During the first week, I deliberately seed in a few specific places.
- note (long-form blog) — Instead of a launch announcement, I publish a "what I learned building this app" post. The story of how something was built tends to outperform the announcement of the thing itself
- stand.fm (audio) — A five to ten minute audio segment about why I built the app. Voice carries the developer's character in a way that text cannot
- Indie developer Discord/Slack channels — I drop release news in "show and tell" channels, always framed as "feedback welcome" rather than promotion
None of these are quick wins. But once launch-day social fades and downloads dip to two or three a day, this is what brings traffic back. If launch-day posts are the firework, this seeding is the slow-burning fire that keeps the room warm.
Week One: Engineering for the First 10 Reviews
The App Store algorithm is reluctant to surface apps with very few reviews. Conversely, the moment you cross your first 10 reviews, the algorithmic floor underneath you starts to lift. Reaching 10 is the real goal of week one.
Here's the natural review prompt I use in my Rork-built apps:
// Trigger the review prompt only on the third use
import * as StoreReview from 'expo-store-review';
const REVIEW_TRIGGER_COUNT = 3;
async function maybeRequestReview(useCount: number) {
if (useCount !== REVIEW_TRIGGER_COUNT) return;
const isAvailable = await StoreReview.isAvailableAsync();
if (!isAvailable) return;
await StoreReview.requestReview();
// Expected: iOS shows the native review request dialog
// Note: iOS only allows requestReview to display up to 3 times per year
}The key here is the number three. On the first use, the user doesn't yet know if they like the app. By the fifth use, you've missed the window of fresh enthusiasm. Three is the sweet spot where users are starting to think "oh, this is actually useful" — and that's exactly when you want to ask.
I also do something a little uncomfortable: in the first few days after launch, I personally ask friends and other indie developers to try the app and, if they genuinely like it, to leave an honest review. It takes some courage, but I've come to accept that the first three to five reviews are something you have to go and earn directly.
Day 30: Three Numbers to Audit
One month after launch, I always audit three numbers, no matter what.
- Conversion rate (impressions → downloads) — Visible in App Store Connect. If you're below 10%, your store page (especially screenshots and the app icon) has clear room to improve
- Day 1 retention — Of the users who downloaded on launch day, how many opened the app the next day? If it's under 30%, that's a strong signal to revisit the first-launch experience
- Source mix — Of all your downloads, what's the ratio between Search and Social? If you're over-indexed on Social, your growth will stall the moment you stop posting. That's when ASO becomes the next priority
Looking at these three numbers, I make one focused round of store-page optimization at the one-month mark. Add a subtitle to the title. Reorder the screenshots. Rewrite the first three lines of the description. These small, unflashy revisions are exactly what turns the first 100 downloads into 200 or 300.
The First 100 Downloads Are Won by Design, Not Marketing
After years of building and shipping apps, I've come to a firm conclusion. The first 100 downloads are almost never won through post-launch marketing. They're decided by what you set up before launch.
Build the landing page. Schedule the social posts. Pre-announce in communities. Implement the review prompt. Take the screenshots seriously. None of these are flashy on their own, but together they're what carries you through the silence.
Rork is an excellent tool for shipping apps quickly, but surviving the post-launch world takes time spent outside the tool. Try to give launch strategy as much thinking time as you give the code.
That layered preparation is what eventually turns "an app I shipped" into "an app people remember."
If you'd like a structured introduction to mobile marketing fundamentals from an indie-friendly perspective, Hooked: How to Build Habit-Forming Products by Nir Eyal pairs surprisingly well with this kind of post-launch thinking.