Re: [geolocation-sensor] Support geolocation (especially geofencing) in the "background" (#22)

> Speaking of requirements, I vote for requiring the PWA to be added to the home screen for better user experience from three perspectives:

I'm not sure I agree. This still maintains a pretty huge imbalance between native apps and PWAs. My opinion is that if a native app can do it, then a PWA should also be able to do it (still requiring consent, etc). I don't quite see why we need to make a distinction between the two. I can install an app on my device without it showing up on the home screen and it can maintain all the permissions it wants, including background geolocation. 

Perhaps this is a question of wording, though. There _is_ a distinction  between ["Add to the home screen"](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Installing#add_to_home_screen) and ["Installing PWAs"](Ohttps://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Installing#installing_pwas). I think requiring an app be _installed_ could be a reasonable requirement. It certainly aligns with native apps. That would also allow it to be shown in the list of apps and see what permissions are granted alongside all of the user's other apps. 

Android 11+ has an "auto-revoke" feature that removes permissions from apps that haven't been used in a certain amount of time. This seems like a much better solution, IMO. 



-- 
GitHub Notification of comment by joekrill
Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/22#issuecomment-3109114894 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 23 July 2025 15:25:48 UTC