Smarter Application Compatability Logic
A lot of time using this product is spent on marking applications and drivers as compatible. It would be nice to have some of this automated. For instance if something is an appx loaded in through the store (especially if it is part of the OS install in the WIM) it should automatically be flagged as approved since it is updated or replaced during upgrade (i.e. photos app).
I would also like to be able to take a balance of the highly adopted/support statement be able to directly be taken into account when I get my to-do list of things to review. For example if a version of a product is highly adopted without issue it should be approved or given a tentative approval (i.e. passed community testing) and then you can just quickly sanity check the list to see if the software causes exotic issues in your environment (i.e. a security product) or to accept the community testing (i.e. its just VLC so that is good enough). Maybe have rules like if best effort AND widely adopted then approved.
Lastly, I would really appreciate if every version update of a driver or software product didn't require manual intervention. If I say client 1.1 is tested, then I shouldn't have to do the same for 1.2 unless I set it as mission critical or there is a supported exception found. I cant tell you how annoying it is for regularly updated software like web browsers to cause the work you did yesterday into chaos as you start building pilot groups today and suddenly you lost a few thousand devices from the ready status.