Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More clearly report a package's popularity #1229

Closed
eseidelGoogle opened this issue Apr 23, 2018 · 9 comments
Closed

More clearly report a package's popularity #1229

eseidelGoogle opened this issue Apr 23, 2018 · 9 comments
Assignees
Milestone

Comments

@eseidelGoogle
Copy link

The pana score is nice. But it might also be useful to see how popular/not (perhaps graded on a curve?) a package is.

For example, how popular is:
https://pub.dartlang.org/packages/cupertino_icons
compared to:
https://pub.dartlang.org/packages/flutter_local_notifications
?

I'm trying to walk the user journeys of:

  • "I'm new to Flutter and looking to learn what packages I should know about"
    and/or
  • "I'm a package author and would like to understand how popular my package is"
@isoos
Copy link
Collaborator

isoos commented Apr 23, 2018

The popularity score - which is part of the final "promoted" score - of the former is 100, while the later has 37, which can be seen on the analysis tab.

For the 1st journey, I think the landing page with the most popular package is a good start, maybe an editorial list of packages would also be helpful, but that is certainly not based on score.

For the 2nd journey:

  • Is the score too hidden/subtle?
  • Do we need to have more explanation around it?

@eseidelGoogle
Copy link
Author

I see, so the popularity score already exists and is graded on a curve?

I guess I was expecting something on the main page page saying "this package is really popular" or similar. 🔥 🔥 But I see now at least some of the data is there.

Maybe there isn't anything to do here at this time.

Maybe I was expecting to see "this is the 337th most popular package, hence your score is 37/100 for popularity". I can file a separate bug for something like that.

@jakobr-google jakobr-google added this to the Backlog milestone May 2, 2018
@isoos
Copy link
Collaborator

isoos commented Jun 27, 2018

I am separating this into two issues:

First, it would be nice if we had a quick visual indication of a package's popularity alongside the overall score. Usually if the overall score is high, it is high because a package is both good quality by our current metrics and it is popular (compared to other packages). However there are cases where the package is out of date, yet popular (for example: bignum, and such icon would make that clear without clicking through to the analysis tab.

screen shot 2018-06-27 at 16 42 32

Instead, we could use the fire emoji there:

screen shot 2018-06-27 at 16 45 57

@mit-mit: wdyt?

Second, we need to update the display of the scores on the analysis tab, and explain better what's going on there and why the score works the way it works.

@mit-mit
Copy link
Member

mit-mit commented Jun 28, 2018

I like the fire overlay!

@eseidelGoogle did you make it to the 'score/analysis' tab, but did not understand the Popularity score shown there, or did you not think the score was clickable and thus did not discover that tab?

@suburbanworrier
Copy link

suburbanworrier commented May 7, 2019

I ended up here trying to figure whether Stagehand's popularity score of 37 is accurate?
In terms of a user trying to figure the importance of various parts it wouldn't fare very well with it overall ranking of 67 - I'd likely disregard it in an initial sweep.

Given that Stagehand does the heavy lifting at the start of every(?) ide-created project I would have expected a much, much higher popularity figure (not having the first idea how you collect popularity data).

edit - found the first idea https://pub.dev/help#scoring

@mit-mit
Copy link
Member

mit-mit commented Apr 24, 2020

I believe we have two separate issues:

  1. We don't clearly report the popularity measure for a package on list and detail pages. I'm tilting the current issue to cover that
  2. We report only a very indirect popularity measure, and not the raw downloads. That is covered in Improved metrics: Measure and report the download count #2714

@mit-mit mit-mit changed the title Would like to be able to understand a package's popularity More clearly report a package's popularity Apr 24, 2020
@mit-mit
Copy link
Member

mit-mit commented Apr 24, 2020

@isoos assigning this to you as I believe the reporting issue is part of the current redesign.

@mit-mit mit-mit modified the milestones: Backlog, Q2 2020 Apr 24, 2020
@isoos isoos modified the milestones: Q2 2020, Q3 2020 Jun 17, 2020
@isoos isoos closed this as completed Jul 30, 2020
@jorwan
Copy link

jorwan commented Jan 6, 2021

Can I see how many download have it ?

@iapicca
Copy link

iapicca commented Oct 13, 2024

this issue seems to be addressed in this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants