- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Mar 2018 11:56:58 +0000
- To: public-device-apis-log@w3.org
I'll provide my personal perspective to this particular question with my chair hat off: >How do you ask the user a question that is both concise and accurate enough that the user's consent is meaningful? Implementers who think prompts provide a good UX for their users are encouraged to do user studies on different strings for prompts to better understand what would work for their users. I feel this questions is not something a web specification should provide an answer to. Some implementers might wish to innovate further in terms of the UI. Since the spec does not mandate any specific strings or UI patterns to be used for user consenting, implementers are free to implement e.g. a tutorial the user has to click through on the first use of a particular sensor API to ensure s/he's aware of the potential risks. My hunch is an animated guide would work much better than any string. That said, I leave it to interested implementers to do a user study on that topic. What I can say is such an on-boarding experience is a common convention in mobile apps on the first use, and people seem to get it, since that pattern is proliferating. My suggestion is the sensor specifications stay agnostic with respect to UI details, and instead provide needed hooks for implementers (Secure Context, Permissions API, Feature Policy etc.) and use an appropriate API design (e.g. non-blocking) to allow UI innovation to happen. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/sensors/issues/352#issuecomment-370758562 using your GitHub account
Received on Tuesday, 6 March 2018 11:57:01 UTC