3 ms·
It's a common practice to do this "just in case" you need the permissions later on. When first installing an app users are likely to hit Ok to whatever, but wh
by rco8786 12y ago
It's a common practice to do this "just in case" you need the permissions later on. When first installing an app users are likely to hit Ok to whatever, but when permissions change on an update they are hit with another screen that tells them the specific thing you are now asking permissions for.
- socrates2015 12y agoIf the author is correct, then Uber is not only asking for permission but actually reading all the information and sending it back to its servers.
- api 12y agoSounds like classic poor security UX design -- it encourages people to allow everything, and encourages apps to claim everything.
- TillE 12y agoI have a lot of issues with iOS, but I think Apple's UX here is clearly superior: it asks you about each individual permission an app requests (not on install, but when the permission is first used), and allows you to deny it.
- dvhh 12y agoWasn't that almost the same approach with UAC ?
- r00fus 12y agoAs usual, Microsoft did it first, but got the UX all wrong. Apple comes along does something very similar, but because of the App Store and the infamous review cycle, can enforce some semblance of control over the app ecosystem. Notice: Apple only does this fairly granular security on iOS, and OSX is much more similar to how Windows it.
- api 12y agoUAC overdid it.