Expected ratio of ServiceWorker instances to Geolocation Updates

Question

EDIT: There is a new version of my Brotkrumen Web App in the same location.

Most important design/proposed-specification change is that TravelManager subscription sh

Answer 1

A: Yes, the example code demonstrates conclusively that the Service Worker paradigm is ideally suited to delivering the much vaunted Background Geolocation to Ultimate Web Apps. The renewal of the SW instance expiry timer for each new position update is key to SW longevity. This is by far the most battery friendly yet feature rich solution available to the Web App background geolocation conundrum.

Note: I recommend a separate TravelManager instance per client (unlike the POC example) and Flex Box styling.

Let's hope this gets picked up by UA suppliers ASAP!