Context Navigation

Changes between Version 1 and Version 2 of Ticket #6511, comment 183

v1	v2
1	1	This discussion is a good example of why having the raw install count alone isn't particularly useful. What plugin developers really need is some context around it: is the plugin growing, slowing down, how does it compare with similar plugins, and what might be affecting that growth?
2		I've been looking at this myself while building [~~StatWP](statwp.com~~). It started around tracking plugin growth and WordPress.org data, but it became clear that there are other useful signals around the same problem too, such as keyword rankings, competitor comparisons, and ways to improve how a plugin communicates its value through its WordPress.org listing and readme.
	2	I've been looking at this myself while building [https://statwp.com/](StatWP). It started around tracking plugin growth and WordPress.org data, but it became clear that there are other useful signals around the same problem too, such as keyword rankings, competitor comparisons, and ways to improve how a plugin communicates its value through its WordPress.org listing and readme.
3	3	I still agree with the main point here: this kind of data should ideally be available directly from WordPress.org. But in the meantime, it's interesting to see how much more useful the existing public data becomes when you have historical data and some context around it.