For an indie developer whose app is already in the App Store or Google Play: what to fix first, which channels to try in what order, and what 90,000+ low-star reviews say about positioning.
To get users for your app, fix the store page so a stranger understands the app in one screenshot, then send 50 targeted visitors a week from places where people already complain about the problem. Rank the work in that order: store listing, direct outreach, communities, short video, launch sites, press and roundups, and only then paid installs. Paid comes last because it multiplies whatever retention you already have, including zero.
An app user is a person who installs your app and opens it at least once. A download is only the first step. This guide is for an indie developer whose iOS or Android app is live with few downloads. It combines public developer threads with a November 15, 2026 read-only analysis of 90,000+ low-star App Store and Google Play reviews in BigIdeasDB. The channel ranking is editorial judgment for a zero-budget app, not a measured result, and no download figures are claimed.
The best order for an app with no budget is: store listing, direct outreach, communities, short-form video, launch sites, press and roundups, then paid installs. Each rank reflects how directly the channel reaches a person who has the problem, how fast you can test it, and how little it costs. It is an editorial ranking built from the threads and data below.
| Rank | Channel | Cost | Time to signal | Best for |
|---|---|---|---|---|
| 1 | Store listing fix (ASO) | Free | 1-3 weeks | Every app. It multiplies all other channels. |
| 2 | Direct outreach to 20-50 people | Free | Days | Apps with a clear user and a specific problem |
| 3 | Communities and free promo codes | Free | Days to weeks | Niche problems discussed in forums |
| 4 | Short-form video | Free, time heavy | 2-6 weeks | Visual, demonstrable apps |
| 5 | Launch sites such as Product Hunt | Free | One day, then a tail | Backlinks and early feedback |
| 6 | Press, roundups and creators | Free | Weeks | Apps with a story or a unique angle |
| 7 | Paid install ads | Paid | Days | Only after day-7 retention is proven |
To find where your own category’s unhappy users already gather, run the same review screen shown below with BigIdeasDB Discover and read the threads it surfaces.
A new app gets zero downloads because it is invisible in store search, undifferentiated on its page, and unsent to anyone outside the store. Those are three separate problems and they stack. Developers describing the same situation in public threads name all three.
“The app store is hard mode. By default you have no visibility and the install requirement creates friction with a low intent audience.”
The same thread shows the second problem. Commenters did not critique the code. They reacted to what the page promised: one objected to a subscription for something a phone already does, another to an install size that felt out of proportion for a notes app. That is positioning, and it is fixable in an afternoon.
“I have launched my app 30 days ago and got 38 installs ... i don’t think we have any chances without promotion in our days.”
A third commenter in that thread described the initial store push as temporary: after it fades you are left with organic downloads that depend on keywords, and if those go to zero you need to promote. That matches what most indie developers report. The first spike is not a trend, and the flat line after it is your real baseline.
One more question appears in the top-ranked r/startups thread for this head query. A commenter asked:
“Why would someone want to use it rather than just googling?”
If you cannot answer that in one sentence, no channel will fix the problem. Write the sentence first. It becomes your subtitle, your first screenshot headline and your outreach message. The sibling guides on why a SaaS is not getting users and traffic with no signups cover the same diagnosis for web products.
Fix the four elements a visitor sees before scrolling: the title, the subtitle, the icon and the first screenshot. Apple indexes the app name, subtitle and a keyword list, while Google Play indexes the title, short description and long description. Put the phrase a stranger would type into the title or subtitle, and put the problem you solve on the first screenshot.
Change one element at a time and wait a week between changes, or you will not know which one worked. Both stores support testing alternate listings, which is worth using once you have a steady stream of visitors.
Read the 1-3 star reviews of the three largest apps in your category, count the repeated complaints, and make the most common unanswered one the headline of your listing. A complaint that appears in hundreds of reviews and gets no developer reply is a positioning opening, because those users already want something they are not getting.
For the full method, see finding product ideas in negative G2 and App Store reviews and the help guide on analyzing App Store reviews. If you want a tool rather than a spreadsheet, the review analysis tools comparison ranks the options.
| Rank | Method | Strength | Weakness |
|---|---|---|---|
| 1 | BigIdeasDB App Store database and Discover scan | 90,000+ low-star reviews already grouped by category, with reply data | Sample is categories scanned, not every app |
| 2 | ChatGPT, Claude or Gemini on a pasted export | Fast theme summaries for one app | You supply and clean the data |
| 3 | Spreadsheet tagging by hand | You read every review | Slow past a few hundred rows |
| 4 | Store review pages, read directly | Free and current | Only recent reviews are visible, hard to count |
| 5 | Asking users in a DM or survey | Reveals why, not just what | Small samples and polite answers |
The most common complaint in 90,000+ analysable 1-3 star App Store and Google Play reviews is money: 26.0% mention price, subscriptions, paywalls, refunds or being charged. The next largest themes are interface and design at 14.0%, login and account problems at 11.3%, and complaints after an update at 10.3%.
The surprise is what is not at the top. Crashes and bugs appear in 8.7% of low-star reviews, well behind money and interface. Indie developers often spend launch month on stability and polish. The reviews suggest users in these categories are more upset about what they are asked to pay and how clear the app is than about how often it fails.
The split by category is sharper. Reviews were gathered by category keyword, and the same screen run per keyword shows very different top complaints.
| Category | Price / subscription | Login / account | Crashes / bugs | Ads | Developer replied |
|---|---|---|---|---|---|
| Plant care | 45.6% | 9.3% | 4.4% | 6.9% | 31.1% |
| Meditation | 43.4% | 12.3% | 7.1% | 4.0% | 28.6% |
| Fitness | 38.6% | 13.3% | 5.2% | 6.5% | 24.7% |
| Photo editing | 34.1% | 4.3% | 7.6% | 10.2% | 18.3% |
| Travel | 31.9% | 11.2% | 4.8% | 4.1% | 29.8% |
| Dating | 30.6% | 19.4% | 3.6% | 4.1% | 27.2% |
| Finance | 26.3% | 25.1% | 5.3% | 4.2% | 26.3% |
| Productivity | 21.9% | 8.0% | 10.7% | 4.8% | 9.4% |
| News | 19.4% | 8.0% | 9.2% | 17.7% | 15.7% |
Read the table as a briefing for your first screenshot. In plant care, meditation and fitness, roughly four in ten low-star reviews are about money, so a page that says “free to start, no surprise charges” answers the loudest complaint. In finance, one in four low-star reviews is about login and accounts, so a fast, plain sign-in is a selling point. In news, 17.7% mention ads. In productivity, only 9.4% of low-star reviews got a developer reply, the lowest here, which suggests users there feel ignored.
Across all low-star reviews with a stored reply field, developers answered 22.7% (22,579 of 99,510). A reply to a negative review is public, and a prospect reading the competitor’s page can see which developer cares. Answering every review on your own app costs nothing and shows up on your page.
A rating caveat matters here. A rating of 0 in store data means the app has no rating yet, not a bad one. In the BigIdeasDB app sample, 35.1% of Google Play apps (1,441 of 4,111) and 3.2% of App Store apps (117 of 3,648) are unrated, so the average rating of 4.28 on Google Play and 4.63 on the App Store covers rated apps only. A new app with no ratings is the normal state, but the ratings that exist show how high the bar is.
Use the state of mobile app pain points for a wider category view, and the App Store database guide to run this screen on your own category.
After the listing, the work is manual and specific: message real people, post where the problem is discussed, and record what each source sends. Keep a simple sheet with the date, the source and the installs it produced. Repeat the one that works and drop the rest after two weeks.
Message people who have the problem and ask for five minutes, not a download. Offer to set it up for them. A commenter on the r/startups thread advised knocking on 20 doors and offering to do the service manually, then asking each user to refer two or three more. For a mobile app, the equivalent is a short, personal message to people who recently complained in a forum about the exact problem you solve. Cold-message tactics for the B2B case are in cold outreach for SaaS.
Answer questions where your user already asks them, and mention the app only when it fits. One developer in an r/iosdev thread reported that posting free promo codes in a giveaway community produced their first 200 downloads. That is a single account, not a benchmark, but the mechanic is sound: free codes remove the price objection and the posts are written for people who want to try new apps. Do not post bare links. Lead with the problem and the answer. Our no-budget marketing guide covers community posting rules in more detail.
Show the app doing one useful thing in under 30 seconds. Name the problem in the first sentence, then show the screen. This is slow compared with outreach and only suits apps whose value is visible, such as editing, tracking or scanning. Post one video a day for two weeks before judging.
Treat a launch as a one-day event with a small tail. It produces a backlink, a quotable launch story and feedback from other builders, but many of them are not your user. The reasoning in is Product Hunt worth it for B2B SaaS applies to consumer apps too: do it after the listing is fixed, not instead of fixing it.
Pitch the people who already write “best apps for X” lists and the creators your user follows. Lead with what is different, offer free access and keep the message to four sentences. One developer in the r/SideProject thread reported silence from every technology blog they emailed, so expect low reply rates and send in batches of ten, not one at a time.
Paid acquisition is the last channel because it sells installs, not retention. Apple Search Ads, Google App campaigns and social app-install formats all work, but they multiply the quality of the product you already have. Run them only when the next section says it is safe, and cap the daily spend small.
Check how many of your first 50 to 100 users open the app again on day 7. If almost none do, paid installs will mostly buy people who leave, and the fix is onboarding and the core loop, not more traffic. Retention is the share of a cohort that returns, and it tells you whether the problem is distribution or the product.
A commenter in the top-ranked r/startups thread framed the same test:
“The first step in something like this is retention and conversion. For the users that have used it, do they come back and/or convert?”
The same commenter added that if existing users are all churning, you have more than a go-to-market problem, and that a value proposition or positioning change may be needed. Use this checklist before any ad spend:
If you are choosing between a subscription and a one-time price, read subscription vs one-time purchase for apps, and check price levels in App Store pricing by country. The review data above is a reminder that price clarity is the most common reason low-star reviewers give.
If retention is healthy but installs are not growing, the issue is distribution and the channel list above applies. If retention is poor in every cohort, the question may be the idea, not the marketing. The app market gap guide and product-market fit guide cover that branch, and problem-solving app ideas shows which problems have documented complaints.
A realistic plan for the first 1,000 users is a 12-week sequence: fix the listing in weeks 1 to 2, run outreach and community posts in weeks 2 to 8 while logging every source, add video and press in weeks 6 to 10, and test paid only in weeks 10 to 12 if retention holds. The numbers are targets for tracking, not predictions.
| Weeks | Focus | Illustrative target | Decision at the end |
|---|---|---|---|
| 1-2 | Rewrite title, subtitle, first screenshot, price copy | Page-view-to-install rate recorded | Does the page convert 50 visitors? |
| 2-4 | Message 50 people, post in 3 communities, give codes | 50-100 installs | Which source sent the most? |
| 4-8 | Repeat the best source, reply to every review, collect feedback | 300-500 total | Does day-7 retention hold? |
| 6-10 | Video and roundup pitches in batches | 600-800 total | Any channel above its time cost? |
| 10-12 | Small paid test if retention holds | 1,000 total | Cost per retained user acceptable? |
The r/startups thread that ranks first for this query offers a similar bar: once you find 400 to 1,000 users, you can send surveys, run interviews and bet on a growth channel. Until then the goal is learning, not scale. A different framing from the same data: 77.0% of the 13,000+ startups with verified revenue in BigIdeasDB’s revenue database earn under $100 in monthly recurring revenue and 90.5% under $1,000. The common failure is not building too little, it is finding no repeatable way to reach users. See how to get your first 100 users for the web-product version of this plan, and TrustMRR for comparable products by revenue.
Before you commit another quarter to one app, run the idea itself through a research pass. BigIdeasDB Discover lists documented complaints for your niche, so you can decide whether to keep promoting, reposition or build something with a clearer gap.
Research retrieved November 15, 2026 with read-only queries. The review analysis used 99,510 1-3 star reviews from 6,700+ apps with reviews (3,193 App Store and 3,523 Google Play), of which 92,390 had text longer than 20 characters. Each review was counted once per matching theme using case-insensitive word patterns, so themes overlap and a review can match several. The review sample was collected by category keyword, so it is not a census of all apps and not a measure of overall star distribution. Download and install counts are not populated in this dataset, so no download figures are reported.
| Evidence | Contribution | Limitation |
|---|---|---|
| BigIdeasDB App Store and Google Play apps (7,700+) and 1-3 star reviews (90,000+) | Complaint theme shares, category split, developer reply rate, unrated share | Keyword-sampled categories; word matches locate passages, not verified causes; historical reviews |
| BigIdeasDB revenue database (13,000+ startups with verified revenue) | 77.0% under $100 MRR, 90.5% under $1K, 2.4% at $10K+ | Web and software startups, mostly not mobile-only; excludes products with no verified revenue |
| r/startups: How do I attract more users to my new app? | Retention-first test, free-first advice, 400-1,000 user threshold | Three-year-old thread; individual opinions |
| r/SideProject: My iOS app has 0 downloads after a month of launch attempts | Store visibility and listing positioning objections | One developer’s app and listing |
| r/iosdev: 13 days after launch | Install counts without promotion, free promo-code anecdote | Self-reported, tiny samples, not a benchmark |
| Google Search results for the head query, November 15, 2026 (US) | Shape of what ranks and the People Also Ask questions | A single day, one market; AI Overview text varies |
| Channel ranking and 12-week plan | Editorial order for a zero-budget app | Judgment, not measured; no case study or conversion data is claimed |
Public sources: the r/startups thread, the r/SideProject zero-downloads thread and the r/iosdev launch-stats thread. The article does not disclose private BigIdeasDB customer or conversion data.
If the listing and channels are fixed and downloads still stall, check the idea itself against our profitable mobile app ideas, the daily frustrations that need an app and the trending app ideas lists, each built from real user complaints.
If installs arrive but growth stalls, read why a product stops growing. For web or B2B products, the channel ranking in how to market a SaaS applies instead.
Start with the store page, because it converts every other channel. Rewrite the title, subtitle and first screenshot around one problem, then send people there from communities where that problem is discussed. Offer free promo codes, answer questions without pitching, and message 20 people who fit your user. Paid installs wait until a small cohort shows it comes back on day 7.
Usually three things stack up. The store page does not say who the app is for, so visitors leave. No keyword in the title or subtitle matches what people search, so nobody finds it. And nothing sends outside traffic, because store search alone gives a new app almost no visibility. Fix the page, then send 50 targeted visitors a week and read the conversion.
BigIdeasDB is the best starting point because it already holds 90,000+ analysable 1-3 star reviews from 6,700+ App Store and Google Play apps, grouped by category, so you can read competitor complaints without scraping. In that data, 26% of low-star reviews mention price or subscriptions. A spreadsheet export plus ChatGPT, Claude or Gemini works for one app, but not for a whole category.
Use BigIdeasDB Discover. It scans a niche against 1M+ complaints and reviews and shows what people dislike in the incumbents, so you see whether a gap exists before you build. In the App Store data, developers replied to only 22.7% of 1-3 star reviews, which marks categories where unhappy users are being ignored. Manual store browsing can confirm a gap, but not find one.
There is no honest average, because it depends on category, price and whether you do outreach. Founders in public threads report 38 installs in 30 days with no promotion and 200 downloads from one free-code giveaway. Plan for weeks of direct outreach, not days. Track weekly installs from each source so you know which channel to repeat.
Only after retention is proven. If fewer than a handful of your first 50 users open the app again on day 7, ads buy installs that leave, and the cost is wasted. Fix onboarding and the core loop first. Once a cohort returns, test Apple Search Ads on your own brand and category keywords with a small daily cap, and compare cost per retained user, not cost per install.
Yes, because it is the one channel that works while you sleep and its inputs are free. Apple indexes the app name, subtitle and a keyword list. Google Play indexes the title, short description and long description. A specific title and subtitle plus a first screenshot that names the problem raise both discovery and conversion. It will not replace outreach for a brand new app.
It is worth a few hours, not a month. A launch brings a spike of curious builders, many of whom will not match your user, and it rarely creates lasting store ranking. Use it for a backlink, early feedback and a quotable launch story. Rank it below store listing fixes, direct outreach and community posts, which reach the people who have the problem.
Before you spend another weekend on promotion, read the 1-3 star reviews of the three biggest apps in your category. BigIdeasDB covers 7,700+ App Store and Google Play apps and 90,000+ low-rated reviews inside a 1M+ complaint, review and discussion corpus. Scan your niche to find the complaint your listing could answer in its first screenshot.
BigIdeasDB Research. (2026). How to Get Users for Your App: 7 Channels, Ranked. BigIdeasDB. Retrieved from https://bigideasdb.com/how-to-get-users-for-my-app