- From: Anton Bessonov via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Apr 2024 21:25:05 +0000
- To: public-device-apis-log@w3.org
> The use cases above all seem like enterprise scenarios. I am not sure why you guys ask for use cases at all? I mean the comment three messages before explains the situation quite well: > I think there are a good number of apps in the Apple App Store that might have been implemented as standalone web apps if background location tracking were available to web apps like they are to native apps. Without feature parity native apps will continue to reign. Isn't it enough to learn from real-world use cases? Anyway. I am no longer on the project, but one of the desired use cases was a safety function in a chat application similar to [Uber's share ride](https://www.uber.com/en-PL/blog/share-your-ride/), but for walking/bicycling/driving/any-movement. Another app I recently installed is for finding my car where I left it. > due to the risk of abuse Is there any explanation for that fear? We already have many sensitive APIs such as Notifications, Camera, Audio, and some of them run in the background. What's wrong with asking users for permissions? What's wrong with putting it behind [user interaction](https://developer.mozilla.org/en-US/docs/Web/Security/User_activation)? It's like saying that digitalization is insecure; let's write in stones 🤷 -- GitHub Notification of comment by Bessonov Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/22#issuecomment-2030580593 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 April 2024 21:25:06 UTC