Your App Is Live: How to Get Your First 1,000 Users

A new app's first 1,000 users rarely come from one channel. They come from a store listing that turns visitors into installs, a landing page that sends web traffic into the app, founder-led outreach, and a referral loop. Paid advertising comes last, once activation and retention show that the users you buy will stay.

This guide is for founders whose app has just gone live on the App Store or Google Play and who need their first users without wasting budget.

What should you measure before chasing users?

Measure activation and retention before you spend on acquisition. If users install and leave, more installs only make the problem more expensive.

• Activation is the first moment a new user gets the value the app promises: a first booking, a first saved document, a first completed workout. Define it as one event and track it.
• D1, D7 and D30 retention is the share of users who started on a given day and come back one, seven and 30 days later. Read it by cohort, grouping users by the week they installed, so you can see whether changes help.
• The funnel: store page visitors, installs, sign-ups, activations and a second session. Both stores report the first two; your analytics must cover the rest.

Published retention benchmarks vary widely by category, region and source, so this guide doesn't quote any. Compare each cohort against your earlier ones. The signal you want is a retention curve that flattens rather than sliding towards zero.

How do you optimise an App Store and Google Play listing?

App Store Optimisation (ASO) means using the text fields that stores index for search, and making the screenshots explain the app in seconds. Each store indexes different fields.

App Store (Apple, accessed Oct 2026):

• Name and subtitle: up to 30 characters each. Put the brand and the main use case here, for example "Brand: Book Local Cleaners".
• Keywords field: 100 characters, terms separated by commas without spaces. Apple suggests avoiding plurals of words you already use, category names, the word "app" and duplicates. Competitor names and irrelevant terms are not allowed.
• Promotional text: up to 170 characters, editable without an update. Apple says it doesn't affect search ranking.
• Screenshots and previews: up to 10 screenshots and up to three previews of up to 30 seconds. Most visitors judge the first few, so lead with the outcome, not the login screen.

Google Play (Play Console Help, accessed Oct 2026):

• App name: 30 characters. Short description: 80 characters. Full description: 4,000 characters.
• Google Play has no keywords field, so write the description for people, using the words they search with. Google warns that repetitive or irrelevant keywords in the name or description can lead to suspension.

How do you get ratings without annoying users?

Use the official in-app review prompts, and trigger them only after a user has just succeeded at something. Both stores limit how often the prompt appears.

• Apple: you can prompt for ratings up to three times in a 365-day period, through the standard system prompt. Apple recommends asking when users have completed an action, level or task, without interrupting them (Apple, accessed Oct 2026).
• Google Play: the In-App Review API has a time-bound quota whose value Google doesn't publish and can change. Google says not to put the review flow behind a button, because the dialog may not appear. It also says not to ask questions such as "Do you like the app?" before showing the prompt (Android Developers, accessed Oct 2026).

Reply to reviews, especially critical ones. On the App Store, the reviewer is notified when you respond and can update their review.

What are custom product pages and store listing experiments?

They let you show different store pages to different audiences, and test which version converts better. Both are most useful once you have steady traffic to test with.

• Apple custom product pages: up to 70 extra versions of your product page, each with its own screenshots, promotional text and previews. You can assign keywords so that a page appears in search results for those terms, and send Apple Ads traffic to a specific page. The metadata is reviewed, but separately from app updates (Apple, accessed Oct 2026).
• Apple product page optimisation: test up to three treatments of your icon, screenshots and previews, one test at a time, for up to 90 days (Apple, accessed Oct 2026).
• Google Play store listing experiments: run one default graphics experiment or up to five localised experiments at a time. Each tests up to two variants against your current listing, measured on installs or other user actions (Play Console Help, accessed Oct 2026).
• Google Play custom store listings: up to 50, targeted by country, by Google Ads traffic or by a unique URL (Play Console Help, accessed Oct 2026).

A practical use at launch: one custom page per audience you approach. A UK tradesperson and a homeowner need different first screenshots.

Why do you need a launch landing page?

Most of your early traffic arrives on the web, from outreach, posts, press and search. A landing page lets you explain the app properly, collect email addresses from desktop visitors and send phone visitors to the right store.

• Store badges for phones and a QR code for desktop, so a laptop visitor can scan straight to the store.
• A Smart App Banner on iPhone. One meta tag shows a banner that opens the App Store, or opens the app if it is installed (Apple, accessed Oct 2026).
• Universal Links (iOS) and App Links (Android), so a shared link opens the right screen in the app. Both are the platforms' own standard for deep links (Android Developers, accessed Oct 2026; Apple Developer, accessed Oct 2026).
• Useful pages for search, such as how the app solves a specific problem, can bring visitors for months after launch.

How do you build a referral loop?

Reward both sides, and pay the reward when the new user activates, not when they install. That way you fund users who stay, and fraud costs more than it earns.

1. Choose the moment users are happiest, usually just after their first success, and ask then.
2. Give each user a personal code or link that opens the app on the right screen.
3. Reward both people with something that costs you little and keeps them using the app, such as credit or a free month.
4. Track invites sent, invites accepted and activations from referrals.

How should founders do outreach and use communities?

In the first weeks, nothing beats the founder personally bringing in and onboarding users. Personal contact also tells you why people leave, which no dashboard will.

• Start with your interview list and waitlist. Email each person individually with a link and an offer to help them set up.
• Onboard the first users yourself: a call, a WhatsApp message or a short screen-share. Write down every question they ask.
• Go where your users already talk: trade associations, local business networks, Slack and Discord groups, subreddits and LinkedIn. Read each community's rules first, and contribute before you post a link.
• Ask early users for introductions to one or two people like them.

Is Product Hunt worth it?

Sometimes. Product Hunt's audience leans towards makers and early adopters, so it suits productivity, design and developer tools best. A launch there is a single day of attention on the homepage leaderboard. For a local service app or a niche B2B tool, that audience is usually the wrong one.

If you launch there, follow its rules. Product Hunt says 12:01 am Pacific Time is the best launch time for makers who are prepared. You cannot ask people directly to upvote, only to visit and comment. Makers are encouraged to hunt their own products, with no discernible advantage to using a third-party hunter (Product Hunt, accessed Oct 2026). Treat it as one day of attention, not a channel.

How should you approach paid acquisition?

Start with one channel and a small test budget. Optimise for activations, not installs, and judge results on how each cohort retains in your own analytics, because platform reporting on iOS is delayed and aggregated.

• Apple Ads, formerly Search Ads, renamed in April 2025 (9to5Mac, 14 Apr 2025). Ads can appear on the Today tab, the Search tab, in search results and on product pages, and you pay per tap (Apple Ads, accessed Oct 2026). Searchers already intend to download, which makes it a sensible first test on iOS.
• Google App campaigns. You supply text, assets, a budget and a bid. Google builds the ads and shows them across Search, Google Play, YouTube, Discover and the Display Network, optimising for installs or in-app actions (Google Ads Help, accessed Oct 2026).
• Meta app ads. Advantage+ app campaigns use automation to set bidding, audiences and placements, and can optimise for installs, in-app events or conversion value (Meta, accessed Oct 2026). Creative does most of the work, so test several concepts.

Measurement caveats on iOS. On iOS 14.5 and later, apps need permission through App Tracking Transparency to track users or access the advertising identifier (Apple, accessed Oct 2026). Apple's attribution frameworks, AdAttributionKit and the older SKAdNetwork, measure campaigns without that permission. With AdAttributionKit, the signed postback contains no user- or device-specific data, and the minimum delay before an ad network receives one is 24 to 48 hours (Apple, accessed Oct 2026). So avoid daily optimisation on iOS. Compare weekly cohorts, and ask "How did you hear about us?" during onboarding.

See also: Performance marketing

How should you use push notifications?

Ask for permission at the moment its value is obvious, send fewer messages than you think, and make the first ones useful rather than promotional.

• On Android 13 and later, notifications are off by default for new installs until the user grants permission. Google advises letting people get familiar with the app first, and linking the request to an action, such as placing an order or following someone (Android Developers, accessed Oct 2026).
• On iOS, Apple's guideline 4.5.4 says push must not be required for the app to work or carry sensitive personal information. Promotional pushes need explicit opt-in through consent language in the app, plus a way to opt out (App Store Review Guidelines, accessed Oct 2026).
• Etiquette: send transactional messages (booking confirmed, order on its way) before marketing ones, respect the user's time zone, cap the frequency, and let people choose categories in settings.

When should you stop paying for users?

Stop or pause paid acquisition when paid users don't activate or retain like the users you win yourself, or when the cost per activated user exceeds what a user is worth to you over a payback period you can afford.

Specific signals:

• Paid cohorts' D7 retention sits well below organic cohorts' for several weeks.
• Each budget increase buys fewer extra activations than the last.
• Reviews and support messages point to a product problem, not an awareness problem.

Paid acquisition amplifies what already works. If retention is falling, put the budget into onboarding and the product, then test again.

A 30/60/90-day plan for your first 1,000 users

Days 1–30: measure and convert

1. Define activation, set up analytics events and build a weekly cohort retention report.
2. Rewrite the store name, subtitle, keywords and first three screenshots, and add the in-app review prompt after the first success.
3. Publish the landing page with badges, a QR code and a Smart App Banner.
4. Personally invite and onboard your waitlist and interview list.

Days 31–60: loops and communities

1. Launch the referral programme, rewarding activation.
2. Take part in two or three communities where your users already gather.
3. Create a custom product page or custom store listing for each main audience.
4. Fix the biggest drop-off in onboarding.

Days 61–90: test paid, carefully

1. Run one paid test (Apple Ads or a Google App campaign) on a fixed budget, optimised for activation.
2. Compare the paid cohorts' retention with your organic cohorts.
3. Scale the test, change it or stop it, using the rules above.

Frequently asked questions

How long does it take to get 1,000 users?

It depends on the category, the audience and how much demand already exists, so any fixed number would be a guess. The plan above aims to show within 90 days which channels work.

Should I pay for installs at launch?

Not before you can measure activation and retention. Paying before that buys installs you cannot evaluate.

How often can I ask for an App Store rating?

Apple's system prompt can appear up to three times in a 365-day period. Google Play applies an unpublished quota, so don't trigger its prompt from a button.

Is Product Hunt worth it for a consumer app?

Usually less than for tools aimed at makers and early adopters. Treat it as a one-day spike, not a channel.

What is a good retention rate?

Benchmarks vary too much by category and source to be reliable. Compare each cohort against your earlier ones and look for the curve flattening.

Why is my iOS ad data delayed?

With AdAttributionKit, an ad network receives a postback at least 24 to 48 hours after the conversion event, and the signed data contains nothing user- or device-specific. Judge campaigns on weekly cohorts.

About the author

Arjun Raj is the founder of Digital Architect, a web, app and digital marketing studio founded in 2023 and headquartered in LB Nagar, Hyderabad, with a studio in Bengaluru. The team builds and markets apps for clients across India, the US, Canada and the UK. Arjun holds a B.Tech in Computer Science and Engineering, specialising in cybersecurity, from IIT Guwahati. More about Arjun

Just launched? Tell us what the app does, who it is for and what you have tried so far, and we will tell you where we would focus first. See our app development work or talk to Digital Architect.