How POPULARITY percent number works in pubdev?

Viewed 724

I read this from their doc https://pub.dev/help/scoring

Popularity:

It is a measure of how many developers use a package, providing insight into what other developers are using.

Popularity measures the number of apps that depend on a package over the past 60 days. We show this on a normalized scale from 100% (the most used package) to 0% (the least used package), but are investigating if we can provide absolute usage counts in a future version.

Although this score is based on actual download counts, it compensates for automated tools such as continuous builds that fetch the package on each change request.

But I would like to know if after those 60 days, the old download counts are lost. If so, that means popularity number will get down too. Can I say that ?

2 Answers

IMHO Yes. That is reasonable - if a package is outdated and people do not like to use it, then it is not that popular now even if it was.

The only thing I would like to point out is that, unlike other package sites, Dart pub dev hides the real statistics about package downloads (replacing this with magic calculation formulas from Google).
What exactly they want to achieve this is not clear. Despite the fact that the developers has already been asked this question several times.
Everything that I heard from them in response was only excuses.

P.S.

They also really dislike non-universal packages and deliberately lower the rating without any hesitation.

That is, if you develop and publish a package that will contain a library that will refer to dart:io you are 100% guaranteed that the rating of your package will be forcibly understated.

What is the reason for this discrimination? Google provides only one reasonable answer to this question:
Consider supporting multiple platforms:
Package not compatible with runtime js

That is, according to Google, for example, the package that will provide information about the device's resources and the operating system is so defective that it does not deserve the highest rating, only because this package is completely useless in browser (not compatible with runtime js).

The rating of such a package will always be 10 points (out of 110 possible) lower than other packages.

I don't even want to waste my energy on developing packages using dart:io given this attitude from Google.

Related