Any plans to continue this in the future? Any alternatives?

collimarco commented 7 years ago

Is this spec completely abandoned? Are there any plans to implement this in the future?

It would be great to have such a future together with the Push API. At Pushpad many customers ask similar futures to trigger notifications based on the user current location.

Otherwise, are there any alternatives to track the user location? I know about the Geolocation API, but the problem is that it doesn't provide a way to track the user location in background (not only when the user is visiting the website). I mean, it would be great to have a combination of the Geolocation API with service workers to constantly monitor the area where the user is located. For example it would be useful to have a service worker event like onlocationchange that can send the new coordinates (obtained with the Geolocation API) to the server.

JamesLMilner commented 6 years ago

I also think that geofencing/georeferencing would be a very powerful addition to the Service Worker use cases, allowing for closer parity with the capabilities of native devices. It would be great to hear more about how this might potentially get picked up again.

robbie-mac commented 6 years ago

@marcoscaceres and @mkruisselbrink I see a lot of value to something like this API, and I am wondering how best to resurrect/get involved in the process? What is the procedure and requirements?

marcoscaceres commented 6 years ago

Please continue the discussion here: https://discourse.wicg.io/t/proposal-expose-geolocation-to-service-workers/2588

We can potentially do it as a community group.

w3c / geofencing-api

Any plans to continue this in the future? Any alternatives? #28