W3C home > Mailing lists > Public > public-device-apis-log@w3.org > May 2021

Re: [geolocation-api] Background Geolocation (#74)

From: Tom333Trinity via GitHub <sysbot+gh@w3.org>
Date: Thu, 06 May 2021 02:39:54 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-833182704-1620268792-sysbot+gh@w3.org>
Thanks for re-opening @marcosceceres. I really appreciate it!

With regard to what's new: -
1) The Alternatives to the TravelManager solution have proven insecuer, unwanted, undeliverable and/or unworkable
2) Use Case and user demand has swollen to the point of utter frustration, forcing many devs to Native App solutions (See links above)
3) There will never be a CPU wake lock as deemed by all UA providers
4) The screen wake-lock is the most battery-unfriendly and inefficient solution that few Background Geolocation Use Cases require
5) Five Long years have passed with no progress https://github.com/w3c/geolocation-sensor/issues/44
6) At the OS level Android and iOS hav cracked down on even native Apps receiving too many Geolocation events

What's the same: -
1) The truth is not relative. The TravelManager was the correct solution then and it remains so today.
2) The sheer beauty of having the UA receive GPS updates rather than a Client or Service Worker means event throttling is out of the DEV's hands
4) Project Fugo means nothing without background geolocation 
5) The TravelManager is also the solution for Geofencing; two for the price of one
6) The user base needs a place to register their dismay at the lack of this essential Web App functionality


-- 
GitHub Notification of comment by Tom333Trinity
Please view or discuss this issue at https://github.com/w3c/geolocation-api/issues/74#issuecomment-833182704 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 6 May 2021 02:40:02 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:58 UTC