How to judge an unrated app

You have found something that does what you need, and the ratings line is empty. No stars, no review count, nothing to read. The instinct is to close the page and keep looking, and that instinct throws away most of the useful software published in any given year.

An unrated app is one that has been released but has not yet collected enough ratings for a store to display a score, which is the normal condition of new software rather than a verdict on it. Ratings are a lagging signal. They tell you about the version other people installed months ago.

There is a real arithmetic problem underneath. Look at any small publisher's catalogue and the pattern repeats: of the 23 apps one developer currently lists across the two stores, only 4 carry any rating at all, and the largest count among them is 39. That is not unusual and it is not a warning. It is what the distribution of ratings actually looks like below the top of the charts.

What a low review count can and cannot tell you

A score computed from a handful of ratings carries almost no information, and it moves violently. One rating of 1 star against 2 existing 5-star ratings drops the average from 5.0 to 3.7. The same single rating against 500 moves it by two hundredths.

That cuts both ways, which is the part people miss:

• A perfect 5.0 from 2 ratings is weaker evidence than 4.3 from 400. The first is two opinions. The second is a distribution.
• A 3.75 from 8 ratings tells you almost nothing about quality. It tells you eight people had mixed experiences, and you cannot see which version they used.
• No rating at all is not a lower score than a bad rating. It is an absence of data, and the two should not be treated as the same thing.

The useful question is not what the average is, but how many people it was computed from and when.

Why the line is empty in the first place

Neither store shows an average until enough ratings exist to compute one that is not misleading. That is a deliberate design choice, and Apple describes the mechanics of how ratings are solicited and reset in its ratings and reviews guidance for developers.

Two consequences follow. A version reset can empty a score that existed, so an established app can briefly look new. And an app can be genuinely popular while showing nothing, because the prompt to rate appears at most three times a year per user and most people dismiss it.

The practical upshot is that the ratings line answers a different question than the one you are asking. You want to know whether the app will work for you. The line tells you how many strangers were willing to tap a star.

So what do you check instead?

Everything a rating would have told you indirectly, you can check directly. It takes longer than reading a number and it is far more reliable.

The version number and its history. An app at 1.0 was released and never updated, or released last week. An app at 2.0.7 has shipped through at least one major revision and several corrections. The store shows the current version and the date it landed; that pair answers "is anyone still working on this" better than any score.

What it asks for. Permissions requested before the app has done anything are the clearest signal available, and they cost nothing to read. A file utility that wants your contacts is telling you something a five-star average never would.

Whether your data can leave. Export is the property that makes a wrong choice cheap. If you can get your work out in a format something else reads, then adopting an unrated app is a reversible decision, and reversible decisions do not need much evidence up front.

The price model, stated plainly. Free with no subscription and no advertising is a real category, and it usually means the app is small, deliberately, and maintained by someone who is not trying to grow it. That is fine. It is also worth knowing before you build a workflow on it.

Who published it. A developer page lists everything the same account ships. A publisher with a catalogue has a reputation to lose, which is a weaker guarantee than a review score but a more durable one.

The trade-off nobody states

Choosing an unrated app costs you a specific thing: you are the one finding the bugs. The first hundred users of any release are doing unpaid quality assurance, and if your tolerance for that is low, waiting six months is a perfectly reasonable strategy.

What you get in return is also specific. Small, new, unrated software is where the single-purpose tools live — the ones that do one job without an account, a subscription tier or a dashboard. Those tools rarely accumulate ratings, because the people who need them install them, use them, and never return to the store page.

So the honest rule is conditional. Use an unrated app freely for tasks where being wrong is cheap: a conversion, a one-off transfer, a utility you could replace in ten minutes. Be slow about it where being wrong is expensive: anything holding your only copy of something, anything with a payment method attached, anything you would have to migrate out of.

When is an empty ratings line actually a bad sign?

Rarely on its own, and reliably in combination. Three pairings are worth acting on.

An old release with no ratings and no updates is an app nobody adopted and nobody maintains. That is different from new. Check the version date, not the version number.

No ratings alongside a large marketing presence is the one to be careful with. An app being pushed hard that has still not accumulated users is a mismatch, and the usual explanation is that the spend is recent and the product is not what the advertising says.

No ratings on a paid app with a subscription is worth pausing over, not because it is dishonest, but because you are being asked to commit money before anyone else has. That is a fine trade at a low price and a poor one at a high one.

For the general method of comparing two candidates once you have shortlisted them, our guide to comparisons sets out the questions in order, and alternatives covers what to do when the obvious choice is wrong for you. If the app is holding real work, the longevity questions in reviews matter more than any of this.

A four-minute routine

Doing this consistently matters more than doing it thoroughly, because a routine you actually run beats a checklist you skip.

1. Read the version and its date. Current version, last updated. Two numbers, ten seconds.
2. Open the permissions or privacy section. Anything requested that the described function does not need is the end of the evaluation.
3. Search the listing for the word export. If it is absent, assume there is none and price that in.
4. Check the price model. Free, one-off, or subscription — and if subscription, what happens to your files when it lapses.
5. Tap the developer name. One catalogue, or one app and silence.

None of this requires installing anything, and it disqualifies most bad candidates before you spend storage on them. For a task where being wrong is cheap, steps 1 and 2 are enough on their own.

The short version

Treat the ratings line as one signal among five, and not the strongest one. An unrated app is a normal app that has not been reviewed yet, and the checks that actually predict your experience — update history, permissions, export, pricing, publisher — are all available on the same page, for free, in about four minutes.