Your App Has Zero Downloads: A Diagnosis Checklist

Every week someone posts a screenshot of an analytics dashboard with single-digit downloads and asks whether the app is bad or simply invisible. The developers who got past that stage almost always give the same answer: stop guessing, split the funnel into three numbers, and fix only the one that is actually broken.

What developers are asking

The same handful of situations come up over and over in r/iOSProgramming, r/androiddev, r/SideProject, r/startups and the app-marketing subs. A habit app four days in with zero downloads. An alarm app with 686 impressions, 46 downloads and no subscribers after a month ¹. A wellness app with 10 downloads and no active users after two weeks ¹⁴. A developer who shipped 25 features and admits he "built for 2 months and marketed for 0 days" ⁸. Another who paid micro-influencers, got likes and comments, and could still name every user ⁹. On X, one game developer summed up a year of hand-made art and code with two words: "2 downloads" ¹⁸.

The backdrop: an analysis shared in January 2026 counted over two million apps and a sharp rise in weekly submissions, attributed to AI-assisted builders ¹⁹. Launching into silence is the default now, not a verdict on you.

Three problems that look identical from the outside

"Zero downloads" is a symptom, not a diagnosis. Experienced developers in these threads separate it into three distinct failures, each with its own fix.

Visibility: nobody sees the listing

Impressions are tiny because the app does not rank for any search, has no ratings, and is not featured. The product page may be fine, but almost nobody reaches it.

Conversion: people see it and walk away

Impressions and page views exist, but few turn into installs. Screenshots do not explain the app, the name hides what it does, the price model triggers resistance, or the positioning is too broad.

Retention: people install it and never return

Downloads happen, but active users stay flat. First sessions end before the "aha" moment, onboarding asks too much, or the app solves a problem people only have occasionally.

How to tell which one you have

Open App Store Connect's analytics and look at four numbers for the last 30 days: impressions, product page views, first-time downloads and conversion rate. Apple defines conversion rate as total downloads divided by unique impressions, and also exposes retention and active devices in the same place ¹⁵. In the Play Console, the equivalent report is store performance: store listing visitors, store listing acquisitions and click-through rate, which replaced the older "conversion rate" metric ¹⁶.

The alarm app had 686 impressions, 270 page views and 46 downloads in its first month; most replies called that normal for a crowded category and pointed at the long 14-day trial and the subscription, not at the funnel itself ¹. An underwater-photo app three days after launch reported 234 impressions, 72 page views and 45 downloads, a 43 percent page-to-install rate, which several developers read as "the page works, go get more impressions" ³. A shift-work app at four downloads a day found its page converted around 17 percent, but it only received about 1,500 impressions a week and ranked in the top 10 for 3 of the 114 searches its developer checked ².

A rough reading rule, assembled from those posts:

• Page views to installs above 20 to 30 percent with low impressions is a visibility problem.
• Thousands of impressions with installs in single digits is a conversion problem.
• Healthy installs with flat active devices and day-one retention far below half is a retention problem.

One more Android detail: the public Play search only exposes roughly 20 to 30 results, so a rank of "47" from a cheap tracker is interpolated, and any keyword outside the top 30 is effectively sending nothing ¹².

Visibility problem: what to try first

Ranking is the lever, and ratings gate ranking. The shift-work developer discovered that his rating prompt only fired after exporting a report, so daily users who just clocked in never saw it; he moved the prompt to the third shift on three different days ². A solo Android developer reported that switching from an in-app banner to Google's In-App Review API raised review counts "significantly", and deliberately avoided review-gating because it violates Play policy ¹¹.

Audit keywords before you change them. The same shift-work developer caught an update that would have renamed the Spanish listing around a term dominated by an app with 31,000 ratings, dropping the clock-in and salary terms he already ranked for ².

Do not buy cheap installs to "look alive". A fitness developer who spent around €300 on Google Ads in low-cost countries, then €500 on Reddit Ads, described bots, instant uninstalls and organic traffic that never recovered ⁵. One reply framed it as "a ghost app with zero installs ranks better than one with 500 installs and 90 percent week-one churn" unconfirmed.

Expect this stage to take weeks, not days. A r/androiddev progress report describes roughly 100 installs from manual outreach and launch sites, then a shift to ASO that took the app to about 8,000 downloads and 1,900 monthly actives at the 12-month mark ¹¹.

Conversion problem: what to try first

Start with the first three screenshots. A team that reached steady organic downloads in week one said the question "what does it do?" from people they tested on in person forced a redesign of exactly those frames ¹³. Put the main keyword in the name; a reply to the micro-influencer post noted that even huge brands append a descriptor to their title ⁹.

Narrow the pitch. The founders of an "everything in one fitness app" were told the all-in-one framing read as generic, and to lead with one user type and one frustration instead ⁷. Use Apple's Product Page Optimization to test icons, screenshots and previews against each other ¹⁷, and change one thing per release; the developer of a content blocker now ranking first for its main term wrote that changing title, subtitle, screenshots and keywords at once teaches you "almost nothing" ¹⁰.

Retention problem: what to try first

Instrument the onboarding funnel before anything else. The Android developer above calls tracking who starts and completes onboarding, and where they drop, the single data point that most improved retention ¹¹. A couples-questions app found a third of new users never opened a single card; version 1.2 shipped one large button that opens the free deck immediately ⁴. The shift-work developer found a feedback survey that could appear on a brand-new user's first session, before the app had done anything useful ².

If installs are fine but nobody sticks, replies split it into two questions: are these the right people, and does the first session match what the marketing promised ¹⁴.

Realistic timelines

The first two weeks are mostly friends. The couples-app developer counted about 140 downloads in month one, almost all purchases in week one from people he knew, and zero paying strangers after that ⁴. Six downloads in two weeks "isn't a product problem, it's a distribution problem; you literally don't have enough data to know if the app is any good yet," as one r/startups reply put it ⁶. The content-blocker app went from about $100 in month one to around $6,000 in month five, and its developer attributes the jump to twenty small changes rather than one event ¹⁰. Budget months, decide which of the three problems you have, and change one variable at a time.

How this shows up in the charts

An app with a few dozen downloads a month is nowhere near any top chart, so treat the charts as the funnel's output, not a goal. On AppWinners you can watch the category chart for a small storefront where your keywords are less contested; a first appearance there in a single country is the earliest external signal that a visibility fix is working. The opposite pattern is just as useful: an app that pops into a low-cost country's free chart for a day and vanishes usually bought installs that did not retain, which is the trap the "giving up" post describes ⁵. Rank history makes both patterns visible without touching your own analytics.