5 ms·
Very unnecessary overreach on android permissions.. Will be interesting to see how many of the fans of uber here on hn will try to spin this. Just forwarded to
by askyourmother 11y ago
Very unnecessary overreach on android permissions..
Will be interesting to see how many of the fans of uber here on hn will try to spin this.
Just forwarded to some friends, they are uninstalling the rogue app as I type this!
- deleted 11y ago[deleted]
- jonathankoren 11y agoIsn't permission overreach du rigueur on Android? Seriously, I thought that this was a preferred engineering pattern on Android due to platform weirdness or something.
- matt-attack 11y agoPretty sure you mean "de rigueur".
- jonathankoren 11y agoyup. fixed ;)
- justinclift 11y agoCheck again. Still needs du -> de. ;)
- jonathankoren 11y agogoddamn it. I'm firing my typist. ;)
- fahrradflucht 11y agoYes it is/was. The problem is/was that your app stops getting auto updates if you add permissions later. A lot of users never go into the update section and grant new permissions and so your app stays on the version with the old permission set for ever.
- jonathankoren 11y agoI knew I wasn't just making it up, and because of that, I'm at -2.
- on_and_off 11y agodepends what you mean with overreach. First : sadly most users (and I really mean most) don't even glance at the permission screen. It makes it hard for us Android devs to push back against the product teams when they want to add a crazy feature needing a ton of permissions (I still do though and the fact that it breaks auto updates at least is a good argument... ). The weird part of the permission system is that we have to transition from a 'designed by & for engineers system where there were a tons of different permissions that no users ever read to a granular system where you only need to ask user's permission in order to access private data. IMO the platform is definitely moving in the right direction (if only because it apes the other platforms approach).