- From: Richard Maher <maherrj@googlemail.com>
- Date: Fri, 2 Dec 2016 07:53:22 +0800
- To: whatwg@whatwg.org, ian@hixie.ch
Cor, steady on Hixie, it wasn’t me yelling that “WHATWG is broken”. All I’m trying to do is get someone (not me) to start development on a solution for background geolocation in HTML5 Web Apps. Sorry if my post was in/pas apropos. > all that matters is the quality of arguments and data presented Excellent news! Here I go: - Secure, user-sanctioned geolocation collection is currently unavailable for HTML5 Web-Apps when they are not running or in the foreground. This leaves the browser hosted applications incapable of competing with Native Apps on an even playing field. The main goal of background geolocation reporting is to allow all web-apps, but in particular, Gaming, Social-Network, and Fleet-Management Apps, to continue to function even if the device has gone to sleep or another App is in the foreground. Additional goals are: - Power-Saving. By using the existing ServiceWorker paradigm and flexible throttle/filter on which geolocation movements are "interesting". - Single-process (Google Play etc) to monitor all geolocation reports for all Apps before deciding if ServiceWorker(s) need to be instantiated. - Unlike Mozilla's current implementation, stalkers, estranged spouses, and marketeers will no longer be allowed to track users covertly. My suggested solution: - serviceWorkerRegistration.travelManager.subscribe({options. . .}) The "options" contain "filter" that can specify such things as minimum distance traveled, minimum reporting interval, accuracy, maximum loiter interval and so on. Once an "interesting" geolocation position change has been obtained a ServiceWorker can be instantiated to process the event in the same way that Push Notifications are handled today. This is where it plugs-in: - https://w3c.github.io/ServiceWorker/#extensibility The following diagram that illustrates how shimlessly typical user movements map to the ServiceWorker paradigm: - Elapsed Time: tttttttttttttttttttttttttttttttttttt User Travelling: P----P----P Stopped P-----P----P Service Worker 1: -------------- Service Worker 2: ================ Now I find that argument compelling! How about you? Cheers Richard
Received on Thursday, 1 December 2016 23:53:55 UTC