Thanks for your detailed list of suggestions and their use-cases.
I will like to address a few of the points that you have mentioned.
According to me, this certainly would be a useful feature but the current API(example) does not support it. Hence, it would be a bit tedious to add this feature but nonetheless if it’s really very useful like say Download counts was, then it will be worth going the extra mile.
I am not sure whether I understood this point correctly but the “Other requirements column” does specify the modules and the version numbers itself.
Yes, I think that’s a bit unclear. We will add a small tool-tip or something of that sort in the next few days.
Basically on selecting the OpenMRS platform version of the user, the blue download button in the screenshot automatically points to the compatible version of the particular module being viewed.
For example, by default , the button points to the latest version of the module(here it’s 4.5).
In this screenshot, there is no OpenMRS platform version selected so the button points to the latest available version of the module.
Here, I have 1.6.6 as my OpenMRS platform version. Hence, the blue button now automatically points to the latest version of that module which is compatible with the user’s platform version(in this case, it’s 3.2).
Hope that makes it clear