[geolocation-sensor] Use Case: Geolocating sports event competitors in real-time (#50)

fadarnell has just created a new issue for https://github.com/w3c/geolocation-sensor:

== Use Case: Geolocating sports event competitors in real-time ==
A valid use-case for our mobile web app would be to track the positions of competitors in sporting events in real-time using the competitors mobile devices. Participants in our events are already using our mobile web app for access to all other information about their event. They've already given consent to share their location. Their location is being shared in real-time until their device sleeps.

We, like most others, are currently dependent on third party devices that geolocate the competitor and transmit data via separate means to cloud services to which we subscribe in order display the current geographic location of each competitor. This creates additional administrative workload, opportunities for failure, duplicative localized bandwidth consumption and increased costs.

Each of our participating competitors has asked why their phones can't do the same - their expectation is for functionality similar to what they experience in their native mapping apps.

We are aware we could develop and distribute companion native apps using existing frameworks, then spawn those or instruct our users to do so. What we would really like is the ability to either;
- allow a PWA Service Worker to run in the background - even if the period must be specified in advance
- allow use of navigator.geolocation.watchPosition() or navigator.geolocation.getCurrentPosition() apis during this describe system-wake-lock state.

Maybe I'm misunderstanding something about the system-wake-lock spec, but it seems a heavy handed way to achieve what is in each case a very specific need. It seems that preventing system sleep, would allow all foreground processes to proceed, regardless of the need of each individual process, where as implementing a special privilege to a service worker might be less resource intensive. I don't pretend to know the details, but it seems we have come really close with PWAs and service workers.



Please view or discuss this issue at https://github.com/w3c/geolocation-sensor/issues/50 using your GitHub account


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

Received on Tuesday, 15 June 2021 09:22:16 UTC