How to Get Your First 100 App Users

The honest frame: a plan we built, results we have not banked

We build in public, so here is the exact status. For SparkQuest we wrote a real go-to-market plan with named channels, TikTok and X as the primary push, plus Reddit communities like r/SideProject and r/androiddev, and week-one targets for downloads, signups, and conversions. Those are targets in a plan, not numbers we are reporting as achieved. So this guide gives you the channel playbook and the 2026 benchmarks to aim at, and it is honest about the line between the plan we made and outcomes we would only claim once we have them. Where we cite a retention number, it is from published 2026 research, not a private dashboard we are dressing up.

Where the first 100 actually come from

Early users come from places where you already have standing or can earn attention honestly. In rough order of how well they work for a solo builder:

• Communities you are already in. The subreddit, Discord, or group where your target user hangs out. r/SideProject and r/IndieHackers for builder tools, a niche community for a niche app. You show up as a member sharing something useful, not a marketer dropping a link.
• Product Hunt and BetaList. A launch concentrates attention into one day and sends a burst of early adopters who like trying new things. Our Product Hunt launch playbook covers the day in detail; BetaList is the quieter, pre-launch sibling for collecting an early list.
• Direct outreach. The least scalable and often the most valuable. Message people who have publicly described the problem your app solves and ask them to try it. Ten real conversations teach you more than a thousand impressions.
• Your own build-in-public thread. Sharing the making of the app on X builds a small audience that is pre-sold by the time you launch.

Notice what is not on the list: paid ads. They come later, and here is why.

Do not buy users you cannot keep

Running ads to cold traffic before you have retention data is paying to learn nothing. You would spend real money acquiring users, watch most of them leave, and still not know whether the problem is the ad, the listing, or the app. Warm channels are better first not because they are free but because they come bundled with feedback: the person who found you in a subreddit will tell you why they bounced. Earn the first 100 by hand, fix what they tell you, and only pour paid acquisition into a funnel that already holds water.

The channels, one at a time

Each warm channel has an etiquette, and getting it wrong burns the channel for good.

• Reddit. The highest-value and least forgiving. You must be a real member first, with a history of helpful comments, before you post your app, and even then the winning post is a story or a lesson, not a pitch. "I built a thing that solves X, here is what I learned" earns upvotes; "check out my app" earns a ban. Post in the subreddit's designated self-promo thread if it has one. r/SideProject and r/IndieHackers are friendly to builders sharing honestly; niche subreddits reward genuine usefulness and punish drive-by marketing.
• Discord and Slack communities. Show up, help others, and mention your app when it is genuinely relevant to a conversation. Communities remember who only ever talked about themselves.
• Direct outreach. Find people who publicly described your exact problem, in a tweet, a Reddit comment, a forum thread, and message them like a person: "You mentioned struggling with X. I built something for that and would value your honest take." Ten of these beat a thousand impressions because each one is a conversation and a potential first user.
• Build in public. Sharing the making of the app on X, the wins and the failures, builds a small audience that is pre-sold by launch. It is slow and it compounds. Our own plan named X and TikTok as the primary push for exactly this reason, and the honest status is that it is a plan we are executing, not a following we are claiming.

The thread running through all four: give value before you ask for attention. Every channel that works for early users punishes the builder who extracts before they contribute.

The retention bar to clear before you scale

The reason to slow down on acquisition is that ranking and word of mouth both follow retention, so leaky apps waste every user you send them. The 2026 benchmarks to orient against:

• Global, all categories: roughly 26 percent day-1, 13 percent day-7, 7 percent day-30.
• Productivity and utility, engaged cohorts: often 40 to 55 percent day-1.

The single most predictive lever is not a clever retention campaign, it is the first session. Research is consistent that day-1 completion of a meaningful first action is the strongest predictor of day-30 retention, and apps that nail first-session activation retain at two to three times the rate of those that do not. The winners deliver value in seconds: a music app plays a song, a meditation app starts a meditation, a notes app opens a blank page. Your job before you scale is to make the first 60 seconds land, then to catch lapsing users inside the 3-to-7-day window when re-engagement still works.

Watch this by cohort, not in aggregate. Group your users by the week they joined and track what share of each week's cohort comes back on day 1, day 7, and day 30. A single blended retention number hides the trend; cohorts show you whether a change to onboarding actually moved the needle for the people who arrived after it. You do not need a fancy tool to start, a spreadsheet and honest counting beat guessing, and the point is simply to know your real first-session completion rate before you spend anything on acquisition.

The 12-tester gate is your first audience

If you are shipping on Android from a new personal developer account, Google now requires closed testing with at least 12 testers opted in for 14 consecutive days before you can apply for production. That is down from the old 20-tester rule that a lot of stale guides still repeat, and the Google Play closed testing guide covers it in full. The reframe worth making: those 12 testers are not a bureaucratic hoop, they are your first cohort. Recruit them from the same warm channels above, and the testing requirement doubles as the start of your user base and your first real retention signal.

A first-100 sequence you can run

1. Recruit 12-plus testers from your communities for the Google Play gate, or for a TestFlight beta on iOS. Watch whether they come back on day 2.
2. Fix the first session until testers reliably complete one meaningful action on their first open.
3. Set your listing so search actually finds you, using the ASO guide, because retention now feeds ranking and a leaky app never climbs.
4. Launch to your warm list, on Product Hunt and BetaList and in your communities, on one coordinated day.
5. Talk to the people who leave. Direct messages, honest questions. This is where the next version comes from.
6. Only then consider paid, once day-1 and day-30 retention are healthy enough that buying more users compounds instead of leaks.

What not to do for your first users

The shortcuts all cost more than they give:

• Do not buy users, installs, reviews, or followers. Bought installs never retain, so they drag down the retention signal both stores now rank on, and bought reviews violate store rules and get detected. You would be paying to rank worse.
• Do not spam communities. One drive-by promo in a subreddit that bans it can burn the channel permanently, and those niche communities are often your best long-term source.
• Do not run ads before you retain. Covered above, and worth repeating because it is the most common expensive mistake: paying for cold traffic you cannot yet keep teaches you nothing.
• Do not fake momentum. Invented user counts and fabricated testimonials are the exact thing we stripped from our own listing in an honesty sweep. They are a trust cost and, increasingly, a rejection.

Early growth that lasts is unglamorous: real conversations, a first session that delivers, and a listing that keeps its promise.

Closing the loop back to ideas

Getting your first users is the last stage of the shipping journey, and it feeds the first stage of the next one. The users who stay, and the ones who leave, tell you what to build next, which is exactly the demand signal our forge grades ideas against. When you are ready to strike the next idea with real evidence behind it, head back to the idea workbench and read how to validate an app idea so your second app starts with the audience your first one taught you to find.

This guide is the growth stage of the whole path. For the complete sequence from finished build to live and growing on both stores, start at how to ship an app in 2026, and when the users start arriving, your ASO and Product Hunt work is what turns a trickle into a habit.