Re: [geofencing-api] Why is geofencing design tied to service workers?

GPS Tracking Use Cases: -

* Can I beseech the browser-developer community at large to please 
contribute their own use cases to this thread?

1) University security have just been told there's a shooter on 
campus. They touch the google maps screen and tell the system to warn 
everyone in a 2km radius to get out or get down. The geoFence has only
 just been created. Pushing the details to the client won't help you 
because the architects are currently considering banning creating a 
geofence around current position as it facilitates quasi-tracking. 
What's more is the time, bandwidth, CPU, and baterry-power wasted 
pushing a geofence to ALL users when most of them are not effected by 
or resident in the danger zone.

2) I want to track my jogging and bike-riding journeys to share with 
friends and manage calories-burned and effort. "Health & Fitness" 
market? Ignore it?

3) I want to know when members of my coffee club are getting close so 
I can start ordering.

4) Let me know if bad weather is moving in.

5) The library is closing. The librarian sends a push message to 
anyone in the building (who hopefully have their notifications on 
vibrate :-) giving clients 15mins to finish up.

6) The next 10 customers to the Guild Tavern get a free beer. No use 
having permanent geofences around every retail establishment that may 
want to communicate with customers.

7) How about a trucking or taxi company wants a central head office PC
 constantly tracking fleet movements in real-time.

8) Pizza Co. want to let users see where their pizza van is. The van 
driver doesn't have to have his phone screen on killing his battery 
for Pete's sake.

Look, I'm not paranoid enough to suggest that W3C members are on the 
take from the Native App providers but, Service Worker developers are 
simply being obtuse if they continue to deny the requirements for 
location tracking and not just a hamstrung, debilitated geoFence API. 
The requestWakeLock() method has it's uses for those who don't care 
about battery life. User/device tracking Apps is not one of them.

The devolved decision-making paradigm inherent in the current 
GeoFencing model is simply incapable of satisfying the legitimate 
business and user requirements. User's want to know more than "Elvis 
has left the building"!


-- 
GitHub Notification of comment by RichardMaher
Please view or discuss this issue at 
https://github.com/w3c/geofencing-api/issues/25#issuecomment-186008595
 using your GitHub account

Received on Friday, 19 February 2016 01:49:31 UTC