How to Estimate Any App's Revenue and Downloads

To estimate app revenue, you model it from public App Store and Google Play signals — primarily how fast an app gathers ratings and reviews, its rank and category, its price, and its monetization model — because neither Apple nor Google publishes per-app earnings. You first estimate downloads from rating velocity and a ratings-per-install ratio, then convert those installs into revenue using price and typical conversion rates for the app’s business model. The result is never an exact dollar figure; it is a defensible range that is reliable enough to compare competitors, validate an idea, or watch a trend. This guide shows the exact inputs, the step-by-step method, the mistakes that wreck estimates, and how to do it without a spreadsheet.

Why nobody can give you an exact number

The honest starting point: there is no public source of truth for how much a given app earns. Apple and Google report aggregate developer payouts but never per-app revenue, and most indie developers do not publish their numbers. So when any tool — including AppNiche — shows you a revenue figure, it is the output of a model, not a leaked statement.

That sounds like a weakness, but it is fine for the questions that actually matter:

• Is this niche worth entering? You need a range and a trend, not a precise figure.
• Which competitor is winning? Relative comparison is far more robust than absolute accuracy.
• Is this app growing or fading? Direction over time survives modeling error well.

The danger is not that estimates exist; it is treating a modeled range as a fact. A trustworthy estimate is one whose inputs you can see and sanity-check — which is the whole philosophy behind a transparent heuristic versus a black box.

The public signals you use to estimate app revenue

To estimate app revenue and downloads, you work backwards from what stores do expose. The strongest signals:

Signal	What it tells you	Why it matters
Total ratings / reviews	Cumulative scale	Rough proxy for lifetime installs
Rating velocity	New ratings per week/month	The single best proxy for current download pace
Chart rank & category	Relative standing	Anchors estimates against known category benchmarks
Price & monetization	Paid, freemium, subscription, ads	Converts installs into revenue
App age & update cadence	Maturity and momentum	Distinguishes a fast riser from a long, slow accumulator

Rating velocity is the workhorse. A million lifetime ratings on a ten-year-old app means something very different from 50,000 ratings gained in the last 90 days. Always look at the rate, not just the total.

Step 1: Estimate downloads from rating velocity

Only a fraction of users ever leave a rating, so installs are some multiple of ratings collected. The ratio varies by category and prompt strategy, but the method is consistent:

1. Measure rating velocity. Count new ratings over a recent, fixed window (for example, the last 30 days).
2. Apply a ratings-per-install ratio. Use a category-appropriate ratio to scale ratings up to installs. Games, utilities, and finance apps each prompt differently, so the ratio is not universal.
3. Cross-check against rank. If your modeled installs would not plausibly support the app’s chart position, adjust. Rank is an independent reality check on velocity-based math.

The output is an estimated download range for the period — say, “roughly 40,000–70,000 downloads in the last 30 days.” Ranges beat single numbers because they make the uncertainty honest.

Step 2: Turn downloads into revenue

Once you have an install range, you layer on monetization. The math differs sharply by model:

• Paid apps: installs × price, minus the store’s commission. The cleanest case.
• Subscriptions: installs × trial-start rate × trial-to-paid conversion × price × expected retention. The most sensitive to assumptions — small conversion changes swing revenue hard.
• Freemium / IAP: installs × paying-user share × average revenue per paying user. Dominated by a small whale segment in games.
• Ad-supported: active users × sessions × impressions × eCPM. Decoupled from installs alone — engagement matters more than download count.

Identify the model before you estimate, because applying a paid-app formula to a subscription app will be wildly wrong. For a deeper treatment of the modeling assumptions and where they break, see what is app revenue estimation.

Step 3: Calibrate with rank and category benchmarks

A raw velocity model floats free of reality until you anchor it. Use chart rank as the anchor:

• Apps at similar ranks in the same category tend to cluster in similar install and revenue bands.
• If your estimate puts a #5-grossing finance app below a #80 hobby app, something is off — recheck the ratio or the monetization model.
• Watch rank trajectory, not just position. A climbing app is accelerating; a sliding one is decaying, and last month’s estimate is already stale.

This calibration step is where good estimates separate from naive ones. Pulling rank, category, and velocity together is exactly what AppNiche’s explore and analytics views are built to do, so you are comparing against live peers rather than guessing.

Step 4: Validate and widen your view

A single app’s number in isolation is fragile. Strengthen it by triangulating:

• Look at 5–10 peers, not one. Patterns across a niche are far more reliable than any single estimate.
• Read the reviews. Sentiment and complaints reveal retention and churn risk that raw install counts hide — review monitoring with topics and sentiment turns this into signal instead of anecdote.
• Check acquisition. An app spending heavily on Meta or Apple Search Ads may show strong installs but thin margins. Ad and creator intelligence shows whether growth is organic or bought.
• Export and model yourself. Pull the underlying numbers via CSV/JSON or the API and MCP tools and run your own scenarios.

This wider lens is the difference between a guess and genuine mobile app market research.

Common mistakes that ruin estimates

• Using lifetime totals instead of velocity. A huge rating count can mask an app that stopped growing years ago.
• Ignoring the monetization model. The same install count produces very different revenue for a $0.99 paid app versus a $99/year subscription.
• Treating a range as a point. “$200k–$400k/year” is information; “$300k/year” pretends to a precision the data does not support.
• Forgetting paid acquisition. High downloads with heavy ad spend can mean low or negative net margin.
• Trusting black-box numbers. If you cannot see the inputs, you cannot sanity-check them — which is why transparency matters more than a confident-looking figure.

Do it without the spreadsheet

You can run this entire method by hand, but the data collection — rating velocity over time, rank history, category benchmarks, monetization signals — is tedious to maintain across more than a couple of apps. AppNiche automates it: download and revenue estimates are derived from public store signals (review and rating velocity, rank, category, price), and crucially, the inputs behind each number are shown rather than hidden, so you can audit and adjust. It covers 760,000+ apps across the Apple App Store and Google Play, with keyword research, review and ad intelligence, and export built in.

Compare it with the alternatives in our roundup of the best app store analytics tools, or start free — no card required — and pull your first estimate in minutes. See pricing for plans, then jump in:

Create a free AppNiche account →

New to the platform? The getting-started guide walks you through your first competitor lookup step by step.