- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2023 11:56:53 +0000
- To: public-device-apis-log@w3.org
@CarelessCourage thank you for these UX ideas on how to approach this problem space. We plan to discuss this issue at our upcoming F2F meeting to check the pulse on where we're at. To set the expectations: this is not an easy problem to solve (as you rightly acknowledged) and further UX work and buy-in from browser vendors is needed to lift this stone. I feel your UX proposals are innovative so I'll bring them to the WG's attention for further ideation. You many be interested in the proceedings of the W3C [workshop](https://www.w3.org/Privacy/permissions-ws-2022/) where we got together to explore this broader problem space around permissions, including various UX challenges. In particular, you may want to check out the [summary report](https://www.w3.org/Privacy/permissions-ws-2022/report) we published. An excerpt from the executive summary: >There was agreement that getting the UX of permission flows right is a core aspect of making capabilities work well, especially as more capabilities get used in web apps and on a larger variety of interconnected devices. There was a desire to incorporate discussions and considerations around UX into standardization work, for example by building a forum in which to seek UX consensus among implementers and the community. You can consider this GH repo to be one such forum where to discuss UX ideas. We'll bring them to the attention of the right folks. Thank you for your contributions. -- GitHub Notification of comment by anssiko Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/22#issuecomment-1699024302 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 August 2023 11:56:55 UTC