Methodology v1

How AppsMining Works

AppsMining tracks directional iOS app signals across multiple markets to help users spot rising apps, developers, and category shifts earlier.

1,000,000+ iOS apps tracked Current public coverage is presented conservatively.
300,000+ monthly active apps Public coverage emphasizes the active app base rather than the full long tail.
Updated daily around 00:00 UTC Latest public snapshot: March 10, 2026.
Downloads · Revenue · URC · Developer signals Multiple signals help users interpret change with more context.

What AppsMining tracks

AppsMining is designed to help users understand which iOS apps are moving, not only which ones are already large.

  • Downloads for estimated app activity over time
  • Revenue for directional monetization performance
  • URC for rating-count or user-feedback activity
  • Developer views for portfolio-level movement
  • Growth windows for 1 day, 3 days, 7 days, and 30 days

Update frequency

AppsMining uses the most accurate public update language available: data is updated daily, with the refresh anchored around 00:00 UTC.

  • Some summaries may lag ingestion because of aggregation or caching.
  • In trend charts, the final point represents the latest available data date, which usually corresponds to the previous UTC day.
Core metrics

Explain the signal, not the magic trick

Downloads

Downloads represent estimated app download activity during a given time window. They are useful for understanding scale, recent movement, and category shifts.

Downloads are not the same as active users, retention quality, or product satisfaction.

Revenue

Revenue represents estimated monetization performance over time. It is useful for identifying commercially strong apps and comparing monetization against download growth.

Revenue estimates should not be treated as exact internal platform truth unless reconciled against verified first-party data.

URC

URC refers to rating-count or closely related user-feedback activity signals, depending on the implementation. It helps check whether growth is accompanied by visible feedback activity.

Rating behavior varies widely across categories and geographies.

Growth rate and growth amount

Growth rate measures relative change between two windows. Growth amount measures absolute increase.

Small apps can show dramatic percentage growth from a tiny base, so growth rate should be read together with growth amount and scale.

Signal language

Multiple signals are more useful than one clever score

Momentum

A blended signal designed to capture short-term acceleration while still accounting for scale.

Breakout

A signal intended to surface apps performing meaningfully above their recent baseline.

Developer momentum

A portfolio-level signal showing whether a developer's broader app lineup appears to be strengthening.

These labels should be read as interpretive aids, not as perfect truth.

Limitations

Important constraints

Estimates are not internal platform truth

Unless AppsMining is working from verified first-party data, values should be read as analytical estimates or trend signals.

Direction often matters more than exact precision

For many workflows, the product is more valuable as a directional tool than as an accounting source of exact point estimates.

Small-base effects can distort rankings

Some apps can look dramatic in percentage terms while remaining small in practical terms.

Category and geography bias are real

Different categories and markets behave differently. Cross-category comparisons should be made carefully.

Rising signals are not guarantees

A strong signal does not guarantee product quality, durable retention, or long-term monetization success.

Use AppsMining responsibly

AppsMining is well suited for generating research ideas, comparing movement, and finding rising apps. It should not be the only basis for investment, legal, or compliance decisions.

FAQ

Short answers to common doubts

Is AppsMining a real-time tracker?

No public claim says that today. The current public wording is daily updates anchored around 00:00 UTC, not real-time.

Does AppsMining cover all iOS apps?

No dataset is perfect. Coverage should be described practically and conservatively.

Are the numbers exact?

Treat them as directional analytical signals unless exact reconciliation exists.

Why do short-term rankings change so much?

Short-term signals are dynamic by design, which is why growth rate should be interpreted together with growth amount, scale, and context.

Why not just use a static leaderboard?

Static charts show who is already large. AppsMining is built to make changing momentum easier to see.

What should this page prove?

That the product understands what it measures, what it does not measure, and how users should interpret the difference.