Thanks Johanna_S too for your feedback! In response to that, I am already working on adding a dependency usage row, so you can instantly see which packages are the most demanded by other packages. That feature borrowed from the Hub is already implemented for each package individually and on demand, and this would replace that and update the entire packages db with this data, on every refresh or application start (I have yet to see performance impact). While not exactly that ideal dream you mentioned, I think it would help a lot in that direction.
About usage statistics, thanks qube21 for the research. I think maybe we could try it as separate application? sort of daemon that sits in background scanning for changes in AddonPackages' date accessed info each X minutes, filling a table with data like package name, date accessed; then build some stats functions around it and send some usage percentage or accumulative 'uses' number to the vambropy db.
But, a thing to consider I do not know yet: if moving a var between directories would change that 'accessed' info it would be inconvenient for true stats, so it would require additional checking, like "if var was moved, do not count it".
Stats by package could then be sent to a vambropy's database field. And the app could optionally activate it.
EDIT: A vam plugin logging those accesses from inside would be the best option IMHO, but I do not now about coding vam plugins.
So, back to work... a lot of work to do lol!
