First 100 Users When 560,000 Apps Arrive in Six Months
Store discovery is crowded, so the first hundred users come from a narrow wedge, quick review cycles, and one channel you can personally work outside the store.

Your app is ready, the screenshots are polished, and the App Store saw about 560,000 new apps in the first half of 2026, nearly the same as the 600,000 released in all of 2025. If you are waiting for the store to notice you, it will not. Your first hundred users are a manual problem.
The wedge is the first hundred
Define the narrowest job your app does for one person. The pitch should name the user, the task, and the trigger in one line. If it needs a second sentence, the wedge is too broad. A broad app competes with every app; a narrow app competes with a few, maybe none.
Do not polish the store page before you know who you are for. The store page only helps after a stranger already has a reason to look. New users need a reason before they arrive. Make the niche small enough that the people in it recognize themselves in the copy. If you build a photo tool, do not say photo tool. Say the exact scrapbook, the exact stamp, the exact ritual.
Pérez launched Stampa, a scrapbooking tool that converts photos into digital stamps, in May 2026 after roughly a week of work. It has been downloaded about 20,000 times and made about $3,000 in profit. That is what a small, clear niche can do when the store page alone cannot.
Review speed is your launch lever
Set a review cadence you can defend. You are done when you have a fixed time from submission to public, a fixed time from first download to first reply, and a fixed time from first bug to fix. Optimize for a fast loop, not a perfect launch.
Apple consistently reviews 90% of app submissions within 48 hours and holds every app to the same quality, privacy, and security bar. Treat that speed as a launch metric, not a hope. Submit early, get the first review, then ask a small group to install it and tell you what they did.
Early users need a person to answer, not a support ticket. Pérez, a Chicago software engineer with no prior mobile app experience, spent five weeks building a prototype and two more preparing InfoDrizzle for the App Store. It earned about 1,300 downloads and roughly $500 in profit. The loop matters more than the revenue: a solo founder can ship, get feedback, and keep moving.
One outside channel beats five passive ones
Choose one channel you can personally work. It should be a place where you can send a direct message, answer questions, and watch installs happen without a budget. Manual outreach is the unscalable thing that works: find the people already asking for the job your app does, and talk to them one by one.
Growth tactics that need scale are the wrong tool for the first hundred. Pick the place where the niche already gathers. Post only when you can answer the next question. Early installs often come from hand-holding: install help, first-use guidance, and a reply that feels human.
Svensson has shipped 11 small-scale apps in the last five months and regards vibecoding as a pastime, not a commercial venture. That mindset helps. Getting to 100 is a conversation problem. A portfolio does not answer the next question. If you can only work one channel, work the one where the user is already present and you can be useful without a paid campaign.
Odds are the budget
Calculate realistic download odds before launch. Finish with a small table: expected installs from the store, expected installs from your channel, and the number of conversations needed to reach 100. Do not treat the store as a guaranteed source. Treat it as a thin source that gets thinner as the app pool grows.
Store downloads rose 2% in the first half of 2026 to 17.6 billion, after growing 3% to 35.4 billion in 2025. Use those numbers to keep your expectations honest. A new app with no distribution can expect a small share of a crowded pool. The outside channel is where you convert attention into installs.
Keep the first-hundred plan in this order:
- Define the niche wedge: one user, one task, one trigger.
- Set review cadence: fixed times for submission, reply, and bug fix.
- Pick one outside-store channel you can personally work.
- Calculate realistic download odds from the store, the channel, and conversations.