3 ms·
This sounds similar to something on iOS 4.2. If you use any part of the asset library framework, which includes something as benign as building a photo chooser
by rbritton 16y ago
This sounds similar to something on iOS 4.2. If you use any part of the asset library framework, which includes something as benign as building a photo chooser for the media library, the device prompts the user to allow access to location services because the photos might have GPS information in them. There is no way to prevent it because the permissions are not fine-grained enough. In the case of the article, the problem could be solved on the OS with the separation of SMS access and operator billing as permissions.
- ben1040 16y agoThere are other permission granularity problems on Android, too. I wrote a streaming media player and want to listen for when the phone rings or goes off hook so I can pause. In order to this I need to access a permission that lets me read IMEI, carrier info, phone number, etc. That's too much info, and it makes my app look skeezy to be requesting access to that when all I want to do is not have music playing down the speaker while the user is on a call.
- panacea 16y agoToo granular and it's an endless set of "are you sure?" prompts which users are likely to develop a blind-spot to... Not granular enough and you grant root-access to everything when you first install a 'flash-light' app. Finding the right balance? Worthwhile.
- JonnieCache 16y agoThere is no separation between operator billing and SMS as I understand it. An "operator billing" payment is simply a very expensive SMS. The differentiation all happens at the provider's end. This makes it a very flexible system, it has been in use pretty much since SMS became popular. How do you think those kids were paying for all those ringtones a few years ago? (before you could just put any mp3 on your phone easily)