Could we ask for several permissions at a time ?

[QuentinFchx]

What if I want to ask 2 or more permissions at the same time ?
Permissions.get(['geolocation', 'fullscreen']) would be nice.

[mounirlamouri]

We could but what would be the benefit over:
Promises.all([Permissions.get('geolocation'), Permissions.get('fullscreen')]);

Slightly less characters for sure but make good usage of current tools the platform provides.

[marcoscaceres]

What @mounirlamouri said, the simpler API is much more composable.

[mounirlamouri]

Let's close this if we agree :)

[QuentinFchx]

From a browser/UI perspective, I guess it would allow to display a custom UI element asking for several permissions at a time.

"À la Facebook"

[mounirlamouri]

Permissions.query() is to check whether you have permissions. This specification does not provide a way to request permissions. Unfortunately, your use cases can't be achieved with the current tools.

[QuentinFchx]

Alright, I confused .query and a sort of .request.
As you mentionned in #4 (comment), why isn't .request a part of this spec ?

[marcoscaceres]

On March 6, 2015 at 2:33:51 AM, Quentin ([email protected]) wrote:

Alright, I confused .query and a sort of .request.
As you mentionned in #4 (comment),
why isn't .request a part of this spec ?

There are strong opinions about .request() ... including IPR concerns, IIRC. We are still trying to see if it can be included. 

[RichardMaher]

Agree very much with @QuentinFchx ! User faticue at a series of pop-up permission questions will be fatiguing. Several permissions will allways have to be requested as a batch at App Start

[marcoscaceres]

Why? The right way to do it is this way: https://techcrunch.com/2014/04/04/the-right-way-to-ask-users-for-ios-permissions/

It an app is asking for permissions in some other way, it's just doing it wrong - but that's not the platform's fault. The app developer just needs to do a better job at providing a good experience.

[RichardMaher]

The jury is in and the recommendations in that article and elsewhere are correct and help deliver the user-experience we all aspire to. As @QuentinFchx implies, perhaps you should lecture Facebook.

Having said that, there is nothing that rules out adhering to those guidelines yet needing to ask for more than one permission simultaneously. For example, my NoteToSelf App is going to want to use the Camera and the Microphone. Do we a) annoy the user twice in rapid succession for a potential string or permissions or b) Explain why the posterity-recording function needs sight and sound?

How about GeoLocation and Notifications, if it's a geofence traversal Usurper Web App. "Hey crazy user Bargain Hunter needs your Location to work out which one of our partners you're next to and Notifications to let you know when there's a red-hot bargain on!
Do you consent to Bargain Hunter accessing your Location and sending you Notifications?"

No brainer!

Or if we decide to tackle the granularity is: - "Usurper needs to access your location to send the ambulance. Do you agree to Usurper: -
[tickbox] Accessing your location while you are viewing the App
[tickbox] Accessing your location while your device is asleep or on a different App
[tickbox] Using accurate GPS readings that may use battery power more quickly

@QuentinFchx I think we need requestAnd and RequestOr

Another good link on UI

[marcoscaceres]

Having said that, there is nothing that rules out adhering to those guidelines yet needing to ask for more than one permission simultaneously.

There is tho: The web platform doesn't really allow that right now. Google did some experimentation with grouping permissions if asked in the same turn of the event loop - I don't know if those experiments went anywhere tho and they just reverted back.

Representation of multiple requests at once are not accepted practice across browsers. In fact, the whole .request() method is so contentious, that Mozilla has repeatedly asked for it to be removed from the spec entirely: #83