@reillyeon from a Chrome perspective, can you please tell me how hard it would be to deliver this TravelManager functionality from your UA?
Analogous to current PushManager implementations, you'd listen for GeoLocation updates in the UA (or a.n.other daemon) and filter them on behalf of clients. Once there is an interesting GPS reading you either spin up a new ServiceWorker or just deliver a TravelEvent to and existing SW.
@reillyeon from a Chrome perspective, can you please tell me how hard it would be to deliver this TravelManager functionality from your UA?
Analogous to current PushManager implementations, you'd listen for GeoLocation updates in the UA (or a.n.other daemon) and filter them on behalf of clients. Once there is an interesting GPS reading you either spin up a new ServiceWorker or just deliver a TravelEvent to and existing SW.
Sounds pretty straight forward eh?
Please see subscribe/unsubscribe example here.
Run it yourself to see very pleasing real-world SW:GPS ratios!