# A million app rows can still miss the app you need

Catalogue size, usable metadata and fresh observations are three different measures of coverage.

By AppRill Editorial · Published 2026-09-08
Canonical: https://apprill.app/blog/app-catalog-size-versus-coverage

A database contains a million app identifiers. How many apps can a customer actually research?

The answer depends on whether those identifiers have names, current metadata, relevant countries and useful observations attached. A row count is a storage fact. Coverage is a product promise.

## Separate the layers

Track discovered identifiers, enriched listings and recently refreshed records independently. Then measure coverage for each evidence type: reviews, rankings, ads, purchase information and revenue observations.

A hypothetical catalogue might have broad listing coverage while collecting reviews for a much smaller subset. That can still be useful if the interface explains it. It becomes misleading when the largest number is used to imply equal depth everywhere.

## Ask about your cohort

A global total can hide weak coverage in the country or category you care about. Build a small benchmark set of real apps from your intended workflow and test search, identity matching, detail completeness and freshness.

Keep unsupported or missing records visible in the result. Replacing an unavailable app with a similarly named one makes the benchmark look better while answering the wrong question.

## Measure the served result

Check what the public application returns, not only what a database query counts. Staged records may be intentionally hidden until enrichment completes. A search index can lag behind the source database. A filter can exclude records for legitimate reasons.

For a product you operate, publish coverage definitions that match these stages. For a tool you are evaluating, ask the vendor what the headline count includes.

More records can improve discovery, but only when identity, quality and retrieval remain dependable. The useful question is whether the product helps you investigate the apps relevant to your decision.

A large number belongs on the dashboard after its definition. It should not have to stand in for the definition.


## Sources