5 ms·
The coarse permissions and alarming text from the OS is a problem with both Android and iOS. Often, an app wants something fairly innocous, but has to ask for
by tyingq 8y ago
The coarse permissions and alarming text from the OS is a problem with both Android and iOS. Often, an app wants something fairly innocous, but has to ask for more, because it's grouped with other things in the same permission ask. Then, the OS message shifts all the blame with scary messages about what the app wants to do.
- creeble 8y agoIndeed. Our app once required location permissions because - get this - a webkit view used for settings used jQuery, which did some kind of screen orientation thing that somehow required location be turned on from the app. I think a jQuery update fixed it, but don't recall. It wasn't simple to track down either. Disclosure: I work on a Sonos competitor [1] that tracks customer data purely for product improvement and is fully opt-out-able. [1] https://www.bluesound.com https://www.bluesound.com
- neilsimp1 8y agoWell I agree lots of times what the app wants is innocuous, I'd still rather have the message than not. Maybe an option to open up a more detailed description of what the app wants the permissions for?
- maxxxxx 8y agoYes there should be much finer detail in permissions.
- ryanbrunner 8y agoWould it have helped in this case? Permissions should convey the privacy risk to the user, not just the technical details of what's happening. To a non-technical user, "Access nearby Wifi signals" (or something similar) sounds totally innocuous. Most people would approve that assuming that the app just wants to connect to the internet. You could get more detailed and say "Access nearby Wifi signals, which could reveal your location", which conveys the privacy risk. But to the average user, "access nearby wifi signals" isn't adding anything - the only real privacy risk is that location is revealed, so it just makes sense to convey it as your location. There's other cases where I think there's a better case for finer-grained permissions - some apps ask for phone call permission just so they can know whether you're a call or not - arguably something that should hardly require permission at all, but it's lumped in with one of the more scary sounding ones.
- maxxxxx 8y agoI agree that the technical details may be difficult to understand but that shouldn’t be a reason to make permissions so broad. I bet if it served ad selling then the permissions would be narrower.
- UncleMeat 8y agoBut we've done research on this. Fine grained permissions don't work, even for people who claim to be knowledgeable. It sounds like a good idea until you look at the papers.
- maxxxxx 8y agoMaybe. At a minimum we should get a log about how apps are using their permissions. I think I am reasonably tech savvy but when I really want an app I pretty much have to agree to all permissions. I don't know how not agreeing will impact app performance.
- tyingq 8y agoWeb browsers let me upload a file without giving me permission as the "app writer" to trawl the filesystem. In this case, the phone OS could provide a similar interface for an app to pass off selection of an SSID or Bluetooth device to the OS, without giving away other permissions.
- kalleboo 8y agoOn iOS, applications are required to submit a reason why they require the permissions which is then displayed to the user along with the permission request. I believe it's also looked at in app review if it's a valid reason.
- maxxxxx 8y agoTotally agree. There should also be a log of what feature apps have actually accessed.
- bjt2n3904 8y ago"Alarming text"? It should be alarming that to play my music with my sound system, I have to give away location data. Frankly, this text isn't alarming enough.
- tyingq 8y agoThe important bit is the granularity. Scary text about permissions that I don't need could be avoided if the permissions were more fine grained.
- blihp 8y agoTwo problems with this assumption per the article: 1) the app previously worked fine without the location information 2) the app no longer works at all without location information. The only legitimate use case for location I can think of would be to pull down cable/tv/radio channel/station listings. But this shouldn't be a requirement since the user could easily manually enter in the ones they want. My guess is that something like this might be used as the pretext for requiring location. However, if the app continues to require location to function longer term (i.e. that this wasn't just an oversight which gets corrected in a future update) then I would assume that the real use case is something that has nothing to do with helping the user.
- icebraining 8y agoThe problem here is that they don't really want location, they just want a list of the surrounding Wifi networks, it just happens that such information is easily converted into a location, so Android requests that permission.
- tyingq 8y agoI don't think they even want a list. Sounds like they'd be happy with a single SSID. Perhaps passed to it the way a browser file dialog works, where the OS sees the list, the app only sees what was selected.
- blihp 8y agoAndroid doesn't request the permission, the app does (via the app manifest) While that is the stated reason, that really isn't a legitimate reason for a remote control app to require location as it might not even work in all network scenarios. (i.e. the device in question may not be using a wifi network the phone can see/use) Keep in mind that many things including trivial flashlight apps have a history of wanting location access. There's usually a pretext in the form of some questionable/marginal feature that's used as a justification for the permission. Often after some digging the real reason becomes apparent in the form of data collection or an included ad serving library. For example, I have a 'smart' thermostat which has an app that requests location access. I deny it and it still works. There's at least one feature they use to justify requesting it but I suspect that if there weren't other uses (having nothing to do with benefiting me) for location data that the feature requiring location data probably wouldn't even exist.
- ryanbrunner 8y agoThis can easily be solved by app developers though. Add a screen before the permission explaining why you want that particular permission, and limit asking permissions to the point that you need to use them rather than the first time the app starts up. Too many apps ask for permission immediately without any context as to why they're doing it.
- tyingq 8y agoThat helps, but I don't feel like it solves it. Technically, for example, an app may not even want to see all available SSIDs. Maybe an app just wants one passed to it. Sort of like a browser file dialog works. The pop up text from the OS says it wants the user's location. That's not what it wants or needs. This comment has some other examples: https://news.ycombinator.com/item?id=19216715 https://news.ycombinator.com/item?id=19216715
- ryanbrunner 8y agoMy point is that we shouldn't base permissions dialogs on what the app intends to do with the data, but what potential risk is introduced with the app having that data. I could make an app that logs every phone call I make along with it's duration so it can recommend friends for me. I wouldn't expect that app's permissions dialog to read "Allow app to recommend friends to you". Getting into the technical details doesn't work for average users, especially for cases like this where the risk isn't obvious - non-technical people will almost certainly not know that revealing local SSIDs reveals your location.
- ken 8y agoOn the iOS App Store, giving a reason is required -- apps will fail review if it's missing, or even if it's not specific enough. https://developer.apple.com/videos/play/wwdc2018/718/?time=891 https://developer.apple.com/videos/play/wwdc2018/718/?time=8...
- moring 8y agoThis is a pet peeve of mine with Android (don't know about iOS). Another example: Browser wants to download a file, so I have to give carte blanche permission to access all my files. Why can't I just give permission to place new files with app-supplied content, i.e. no reading of existing files, no overwriting / deleting of existing files, and OS-managed name collision resolution? The same applies to the camera app. And no, the camera app does not need to read my files to display a gallery of photos taken. The gallery app already does that, and Android is perfectly capable to re-using an activity (via intent) of the gallery app as part of the camera app without the latter gaining any permissions.
- icebraining 8y agoI'm not an Android developer, but I think they've introduced SAF (Storage Access Framework) in 4.4 just for those cases; the app just asks the user for a specific file or directory, which is selected using the system's UI.