Re: Almost every app I consider for installation
Now if only the permissions model was narrow enough. As I understand, and admittedly I'm not an Android developer, required permissions are auto-determined at build time by looking at the dependencies of a project. Given the interconnectedness of services and APIs, you easily end up requiring silly permissions, because some little corner of a library somewhere might need it in specific circumstances...which, of course, may well be totally irrelevant to your app.
My pet peeve with network permissions is that I can't limit the destination. Many apps need/want network access to check for updates/configs/etc. I'd prefer to only allow them to phone home to destinations of which I approve. I've not seen Marshmallow's permissions in action, but a handy popup like "Blah wants to connect to 'tcp://dodgy.site/track/me'. Allow: Now, Always or Never?" would be much appreciated.