Dudley Development

What Does Not Enough Ratings Mean on the App Store?

Not enough ratings means the App Store is not showing a reliable public rating summary yet. It does not prove an app has no users, no downloads, or low quality.

“Not enough ratings” on the App Store usually means one thing: Apple is not showing a reliable public rating summary for that app in the storefront you are viewing yet. It is not proof that the app is bad, unused, abandoned, unsafe, or secretly popular.

A public rating is feedback that some users choose to leave. It is not the same as downloads, retention, revenue, support tickets, crash rate, or product quality. For small apps, newly updated apps, and niche utilities, public ratings can lag far behind actual use.

Sources: Apple’s ratings, reviews, and responses guidance, Apple’s App Store Connect help on resetting an overview rating, Apple’s StoreKit review request documentation, Apple’s App Review Guidelines, and a current U.S. Apple lookup for EconByte: Daily Economics.

The Short Answer

If an App Store page does not show enough public ratings to summarize, read that as missing public feedback, not a verdict.

It can mean:

  • the app is new;
  • the current version is new;
  • users have not chosen to rate it yet;
  • the app has ratings in another storefront but not enough visible signal in this one;
  • the developer reset the overview rating with a new version;
  • Apple simply is not displaying a rating overview yet.

It does not mean:

  • nobody downloaded the app;
  • nobody uses the app;
  • the app has zero revenue;
  • the app has no private support feedback;
  • the app is good or bad;
  • the developer is hiding something.

Apple explains that ratings are one-to-five-star feedback and that the summary rating shown on the App Store is specific to each territory. That territory detail matters. A thin public signal in one storefront is not a global user counter.

Ratings Are Not Downloads

The most common mistake is treating ratings like a public user count. They are different signals.

A download is an acquisition event. A rating is an optional public feedback event. A written review is an optional written feedback event. Those events can move at very different speeds.

That distinction matters for small apps. A useful niche app can have real users and still show no public rating summary because few people review every app they try. A heavily promoted app can get downloads without retention. A polarizing app can collect reviews faster than a quiet utility. None of those patterns can be proven from the “not enough ratings” label alone.

For app makers, App Store ratings should sit beside analytics, crash reporting, support messages, revenue reports, and user interviews. For users, the rating row is a clue, not the whole trust decision.

Why Small Apps Often Show This

Small apps start with a smaller feedback pool. Ratings require a user to experience value, notice the prompt or product-page option, decide the app deserves feedback, and complete the action.

Apple encourages developers to ask at appropriate moments, such as after a satisfying action, level, or task. Apple’s StoreKit review request documentation also says the system may display the rating and review request at most three times within a 365-day period for a user who has not already rated or reviewed the app on that device.

That cap is good for users because it limits nagging. It also means ratings can arrive slowly for apps that ask respectfully.

So if a small app shows “not enough ratings,” the honest read is: public review evidence is thin. Anything stronger needs another source.

Can an App Rating Be Reset?

Yes. Apple says developers can reset an app’s overview rating when releasing a new version.

After a reset, Apple says a message appears on the App Store product page indicating that the rating was recently reset. A new overview rating appears once enough users have rated the new version.

There are two important caveats.

First, Apple says the previous rating cannot be restored after the new version is released. That makes a reset a serious release choice, not a casual cosmetic button.

Second, Apple says written customer reviews continue to display on the App Store. Resetting the summary rating is not the same as deleting review history.

For a user, that means a thin rating overview does not always mean the app has no history. Check version history, written reviews if any are visible, release notes, privacy details, and the developer site.

What to Check Instead

When a rating overview is missing, use a broader checklist.

Check Why it matters
Developer name Confirms who is responsible for the app
Version history Shows whether the app is maintained
Privacy details Shows what the developer says the app may collect
Pricing and purchases Helps avoid surprise subscriptions or confusing unlocks
Screenshots and description Should clearly explain the app’s job
Support and privacy links Give you a place to get help or inspect policies
Written reviews Can reveal bugs, confusion, or praise that a star average hides

If those signals are clear, a missing rating summary is not automatically scary. If those signals are vague, pushy, mismatched, or missing, the absence of ratings gives you less confidence to work with.

What Developers Should Not Do

The wrong lesson is “go get ratings at any cost.” That is how apps end up with spammy prompts, fake reviews, and broken trust.

Apple’s App Review Guidelines warn against manipulating reviews, inflating chart rankings, or using paid, incentivized, filtered, fake, or third-party feedback schemes. Apple also says developers should use the provided review prompt API and disallows custom review prompts.

The better pattern is slower and sturdier:

  • make the app’s value clear before download;
  • ask only after a useful moment;
  • keep support easy to find;
  • answer genuine written reviews respectfully;
  • fix repeated complaints and mention those fixes in release notes;
  • treat ratings as one signal, not the product itself.

That is less dramatic than chasing a star average. It is also a better way to build trust.

Where EconByte Fits

EconByte: Daily Economics is a Dudley Development iPhone app in the Education category. A current U.S. Apple lookup for this article returned EconByte: Daily Economics, bundle com.nsantulli.econbyte, version 1.1.8, free, iOS 16.6 or later, seller Dudley Development, LLC, and userRatingCount: 0.

That public lookup does not prove anything about EconByte’s downloads, retention, revenue, support load, or learning value. It only means the public ratings signal in that lookup is not a visible rating summary.

For a small education app, that is the right interpretation: keep the signal in its lane. Ratings are public feedback. They are not a substitute for usage evidence, support evidence, crash evidence, or reader outcomes.

Download EconByte

Liked this? EconByte is free on the App Store.

Download on theApp Store

Dudley Development makes the app mentioned above. The editorial answer is written to stand on its own.

Frequently asked questions

What does not enough ratings mean on the App Store?

It means the App Store is not showing a public ratings overview for that app in the storefront you are viewing. It is a thin public-feedback signal, not proof that the app has no users or low quality.

Does not enough ratings mean nobody downloaded the app?

No. Downloads, active users, ratings, reviews, revenue, support volume, and crash reports are separate evidence streams. A user can download and use an app without leaving a public rating.

Can developers reset App Store ratings?

Apple says developers can reset an app's overview rating when releasing a new version, but written reviews continue to display and the previous rating cannot be restored after release.

How often can an app ask for an App Store review?

Apple's StoreKit documentation says the system review request can be displayed at most three times in a 365-day period for a user who has not rated or reviewed the app on that device.

Should I trust an app with not enough ratings?

Use it as one small signal. Also check the developer name, privacy details, version history, screenshots, support link, pricing, and whether the app clearly explains what it does.

Keep reading