The nice thing with App-V is that i can make one package (isolated from the environment and OS) and that i manage this package and all settings from within. When i have to manage also the GPO's I have 2 places that I have to manage (The AD and the local install). With App-V when I disable/unpublish the package then everything is gone or not accessible. Some manufactorers write recipies/manuals for making these packages to get a wider support for their product. Also there could be known issues that could be addressed or limitations for using i.e. Chrome as App-V package. The customer can decide what he wants to do. For me who is packaging Chrome for the first time, without a recipy I am searching and trying the installation and see issues that i need to fix. I am not the first one. This is very pitty and expensive. The manufactorer could be of a great help with this. He gets all these questions...
Because of the isolation from the package with the OS this methode gained a lot of popularity and Microsoft invested a lot to get this also integrated in the OS.
When you get an update you make a new package, publish the new and unpublish the old app and you are in business. Without issues of installing/uninstalling the local application. Are there issues with the update you can change this for the Enterprise in 2 minutes. Only the user has to log on again.
Best regards,