Your first 100 users come from people you contact yourself. Two weeks before launch, set up measurement, a feedback channel and a list of 50 named people. On launch day, message them one by one. After launch, talk to the first ten users and fix what blocks them before you chase more.
This is for founders launching a first app, on the web or in the stores. The running example is StudyLoop, an imagined study planner for university students.
In short:
- A personal message beats a public post for the first users.
- Measure the core action, not downloads or page views.
- Show HN rejects sign-up pages and quick one-off projects.
- The first ten users teach more than the next ninety.
Two weeks before: set up what you will need
Most launch-week panic comes from things that take a day to set up. Do them early.
- Define the one action that means a user got value. For StudyLoop: created a study plan for one exam.
- Install analytics that count that action, with the traffic source.
- Add a feedback channel inside the app: a button, an email address or a short survey.
- Write a privacy policy that matches what the app collects.
- Prepare the store listing, screenshots and description if you ship to the stores.
- Test the full first-time flow on a real phone with a fresh account.
For a short in-app survey, tools such as PostHog surveys can ask one question after the core action. Ask "What almost stopped you?" rather than "Do you like it?".
Write a list of 50 named people
The first users are people you can reach by name. Write a list of 50 who fit the customer exactly, with how you'll reach each one.
For StudyLoop, that's students from your course, members of two study societies, a few teaching assistants, and friends of friends at another university. A name and a channel per line. "Students" isn't a name.
Then plan where all 100 users will come from. Lead with direct contact, with public posts as a bonus.
| Source | Target users | How |
|---|---|---|
| Personal list | 30 | One message each |
| Two communities | 30 | Helpful posts, within rules |
| Teaching assistants | 20 | Ask them to share once |
| Store or web search | 20 | Listing and search pages |
These targets are a plan to adjust, not a benchmark. Your mix depends on your customer and your first marketing channel.
Launch day: message people one by one
Send personal messages, not a mass email. Mention why you thought of them, what the app does in one line, and one clear ask: "Could you try it before Friday's exam and tell me what's confusing?"
Expect a lot of silence. Follow up once, two or three days later. A short, specific ask gets more replies than "let me know what you think".
Post in communities by their rules
Communities can bring your next users if you add something first. Read the rules, answer questions, and share the app where it helps.
Hacker News is a good example of strict rules. Its Show HN guidelines say Show HN is for things people can try, not sign-up pages, and ask makers not to post quickly generated one-offs. Read the general Hacker News guidelines too. Other launch sites have their own rules, so check each one before you post.
Store listings work quietly in the background
If StudyLoop is in the stores, its listing does work every day. Write the first line for the search the student would type, such as "study planner for exams".
Both stores let you test listings later. Google Play supports store listing experiments. Apple offers product page optimization. You need steady traffic for those, so they come after the first 100.
For a web app, connect Google Search Console on day one so you can see which searches bring people.
After launch: learn from the first ten
The first ten users are worth hours each. Message every one who completes the core action. Ask for a 15-minute call, and ask three things:
- What were you using before?
- What almost stopped you from finishing your first plan?
- Who else should use this?
Fix the top blocker before inviting more people. If three of the first ten got stuck on the same screen, the next ninety will too.
Track the numbers that predict growth
Downloads feel good and predict little. Watch these instead, every week:
- Activation: share of new users who complete the core action.
- Return: share who come back the next week.
- Referral: users who arrived because another user sent them.
If activation is low, fix onboarding. If return is low, the app isn't solving a frequent problem yet. If both are fine, put more effort into the channel that works.
Launching a GrowApps app
A GrowApps app can go live on the web at a growapps.cloud address, and a findability checklist runs at every publish.
For Android, GrowApps helps with the Google Play store listing, the screenshots, a privacy policy and the signed app file, and you upload it in your own Play Console account (Google Play and the App Store). You can connect your own PostHog or Google Analytics account to count the core action.
Start your list of 50 now
Open a note and write ten names of people who fit your customer, with the channel you'll use to reach each one. Add one sentence you'll send them. You now have the first fifth of your launch list. Next, read how to publish an app to Google Play.
Frequently asked questions
Should I launch on Product Hunt?
It can bring a burst of visitors, mostly makers and early adopters. That's useful if they are your customers. For a study app or a plumbing tool, your time is often better spent on direct outreach first.
Do I need a big launch at all?
No. Many apps start with a quiet launch to a small list, fix what breaks, and grow from there. A big public launch works better once the first users get value without your help.
Sources and further reading
- Show HN guidelines, Hacker News
- Hacker News guidelines, Hacker News
- Run A/B tests on your store listing, Play Console Help
- Product page optimization, Apple Developer
- Surveys, PostHog docs
- Google Search Console, Google
- Do things that don't scale, Paul Graham