4 ms·
The same way we stop native apps from doing that? It used to be fairly common in Android for developers to just request everything. Developers still request to
by danShumway 9y ago
The same way we stop native apps from doing that?
It used to be fairly common in Android for developers to just request everything. Developers still request too much, but it's gotten a bit better because in newer versions of Android you have to actually start using the API before the permission will be requested - so as a user if you request microphone access, I know it's because right now you intend to record sound.
It's a very small improvement, but it helps, and it's pretty much copied wholesale from web's permission model. The web also allows you to grant parts of permissions. When a website asks you for location and camera, you can choose to give it just camera - or you can choose to give it camera for one session and then re-ask the next time the API is accessed.
These are all small steps that make it cumbersome for developers to just say "give me everything or nothing works." The trick is to make it easier for app developers not to think about permissions; and then when you get an app that requests 3 permissions upfront, you know something shady is going on because there just aren't a lot of legitimate reasons to do that anymore.
- deleted 9y ago[deleted]
- repsilat 9y agoYeah, exactly. This works pretty well with location tracking -- few people request it, you can deny the request, and things almost always work fine when you do. (I've had one site lock me out for blocking location data, and some things work poorly on Facebook's mobile site without location tracking on, but I haven't noticed any other problems.)
- imron 9y ago> Developers still request too much .. > it's gotten a bit better .. > It's a very small improvement, but it helps .. > These are all small steps Thereby illustrating the parent's point that developers will still ask for too much and that the power balance is in favour of the developer. Apple on the other hand heavily restricts what developers can do. It's developer-hostile, but user-friendly.
- strangegecko 9y agoYou can be just as user-friendly by giving the user a button "never let web pages ask me again for this / all permissions (you can undo this in settings)" when the first page asks for permissions.
- fnordsensei 9y agoI disagree that this is usable enough. Every webpage and their dog has now started to ask for permissions to popup notifications. I find this really annoying. Sure, I can disable it for one site, but then the next one I visit pops up the same question if it's OK to spam me. I've turned it off browser-wide as a result. If asking for permissions is to be an option in the future, I hope it is a completely manual opt-in, available in some kind of site-specific settings thingie (that makes no effort to distract the user by noises, popups or red badges by itself). I think this is reasonable given the ratio of sites a user should be willing to grant any permissions to, vs the amount they should want as sandboxed as humanly possible.
- strangegecko 9y agoThat's what I said though, you are given the option to opt out entirely, or it could be the default as you said. This can be as fine grained as necessary so it is not intrusive but still allows you to use features if you choose so. What I object to is the Apple approach to simply take away the option whether you want it or not. It's not user friendly at all, it's patronizing and stifling.
- danShumway 9y ago:) Browser permissions are also ahead of mobile on this one. What they're starting to do is force some permission prompts to be behind user actions - so, you can request a permission as a response to a user clicking on a specific type of button, but you can't just request it anywhere. A big reason notifications are spammy is because they don't have those restrictions, I suspect because <tinfoil_hat>Google was heavily involved in their design.</tinfoil_hat> I suspect that browsers will start to move in the direction of "let the user turn this on via a button someplace" as notification prompts become more common. And I suspect that, like with everything else, those controls will get implemented on the web before mobile. You're upset that every website can ask you to display notifications. With native apps on Android, they don't even need to ask. Apps I install are by default allowed to spam me with notifications, and I have to opt-out after the fact. If we're comparing permission models between native and the web, the web is definitely giving users more control right now. I don't understand the perspective of someone who feels safer downloading an app than they do visiting a website.