4 ms·

That model is backwards. If there is one thing iOS got right, it's the permission prompt. Nobody reads those lists and it's hard to know what the intent is with

That model is backwards. If there is one thing iOS got right, it's the permission prompt. Nobody reads those lists and it's hard to know what the intent is without context in the app. Having the app ask on first use makes much more sense. It's much less likely to get away with this. Even better, you can still use the app if you say no. It will just get dummy values back.

Drakim 9y ago
On the flip side, this means you have already installed and committed to having this app on your phone. Lots of people might just press "accept" at that point out of being lazy, instead of uninstalling it and going back to the app store to look for an alternative. If you ask me, both should be in place. When I install an app a list of permissions (and a short text next to each from the developer explaining why they need this permission), along with manual prompting once the app is installed and the thing in question (like the mic) is to be used.
- mrtksn 9y ago
  Asking for mic permission with no apparent reason is scary, many people will not allow it. Also you can easily change it from the settings. Apps on Apple App Store can't stop functioning just because of a permission is not given. If the app can't perform it's function without a specific permission the developer needs to explain it to the users and ask them to go into the settings and lift the ban. So if an app that does not have a really good reason for asking for the mic, the use can just deny that permission and continue using the app. No need for fishing in the sewage until you find the gold among the sh*t and it's my main reason to use IOS over Android(Though I hear its getting better).
- appetizer 9y ago
  Many other people don't click accept for any reason
pidg 9y ago
I think Android 7 does now ask on first use rather than at time of installation.
- samat 9y ago
  1. build you app targeting earlier versions 2. No dialogs in any android version
dtech 9y ago
This works the same since Android 6 (2015)
- ClassyJacket 9y ago
  Only on apps that target Android 6 however. They couldn't retroactively apply it. Just build your app targeting Lollipop and you get all the permissions you want. Plus their app store isn't as strongly vetted, so apps can refuse to work if you don't grant a bullshit tracking permission.
  - 0x0 9y ago
    This I never understood. Couldn't they just supply the app with empty lists and black pixels for restricted APIs until the user approved the permission? iOS managed to do this retroactively just fine.
    - ClassyJacket 9y ago
      I believe they do, but you have to specifically go into your settings and explicitly block the permission for the app and click thru a warning that the app might break, rather than ever being asked. I don't remember when iOS did this retroactively, do you have an example? When have they even added a new permission that wasn't a new API entirely?
    - s73ver 9y ago
      I don't think iOS did it retroactively. It's just that, since so many more people actually update (because they're not at the mercy of their carrier), devs update their apps more often.
      - 0x0 9y ago
        I believe you are incorrect. iOS have introduced more and more permissions (most recently, for iOS10 a permission prompt appears for apps trying to access the built-in media library, whereas this was a silent free-for-all in earlier versions), and existing apps are not grandfathered in. According to at least https://www.macrumors.com/2012/06/14/apple-requires-user-permission-before-apps-can-access-personal-data-in-ios-6/ https://www.macrumors.com/2012/06/14/apple-requires-user-per... apps will just receive empty/dummy data until the permission is granted. From my personal experience, camera APIs return black pixels until the permission has been granted, even for apps that were released when iOS 5.0.0 was the latest version and never updated since.

Drakim 9y ago

On the flip side, this means you have already installed and committed to having this app on your phone. Lots of people might just press "accept" at that point out of being lazy, instead of uninstalling it and going back to the app store to look for an alternative. If you ask me, both should be in place. When I install an app a list of permissions (and a short text next to each from the developer explaining why they need this permission), along with manual prompting once the app is installed and the thing in question (like the mic) is to be used.

mrtksn 9y ago
Asking for mic permission with no apparent reason is scary, many people will not allow it. Also you can easily change it from the settings. Apps on Apple App Store can't stop functioning just because of a permission is not given. If the app can't perform it's function without a specific permission the developer needs to explain it to the users and ask them to go into the settings and lift the ban. So if an app that does not have a really good reason for asking for the mic, the use can just deny that permission and continue using the app. No need for fishing in the sewage until you find the gold among the sh*t and it's my main reason to use IOS over Android(Though I hear its getting better).
appetizer 9y ago
Many other people don't click accept for any reason

pidg 9y ago

I think Android 7 does now ask on first use rather than at time of installation.

samat 9y ago
1. build you app targeting earlier versions 2. No dialogs in any android version

dtech 9y ago

This works the same since Android 6 (2015)

ClassyJacket 9y ago
Only on apps that target Android 6 however. They couldn't retroactively apply it. Just build your app targeting Lollipop and you get all the permissions you want. Plus their app store isn't as strongly vetted, so apps can refuse to work if you don't grant a bullshit tracking permission.
- 0x0 9y ago
  This I never understood. Couldn't they just supply the app with empty lists and black pixels for restricted APIs until the user approved the permission? iOS managed to do this retroactively just fine.
  - ClassyJacket 9y ago
    I believe they do, but you have to specifically go into your settings and explicitly block the permission for the app and click thru a warning that the app might break, rather than ever being asked. I don't remember when iOS did this retroactively, do you have an example? When have they even added a new permission that wasn't a new API entirely?
  - s73ver 9y ago
    I don't think iOS did it retroactively. It's just that, since so many more people actually update (because they're not at the mercy of their carrier), devs update their apps more often.
    - 0x0 9y ago
      I believe you are incorrect. iOS have introduced more and more permissions (most recently, for iOS10 a permission prompt appears for apps trying to access the built-in media library, whereas this was a silent free-for-all in earlier versions), and existing apps are not grandfathered in. According to at least https://www.macrumors.com/2012/06/14/apple-requires-user-permission-before-apps-can-access-personal-data-in-ios-6/ https://www.macrumors.com/2012/06/14/apple-requires-user-per... apps will just receive empty/dummy data until the permission is granted. From my personal experience, camera APIs return black pixels until the permission has been granted, even for apps that were released when iOS 5.0.0 was the latest version and never updated since.