Hacker News Reader

> The use of particle filters necessitates a level of server affinity. Each new request to our service must be routed to the same back-end server for processing in order to update the correct particle filter.

Was implementing this on the client device considered? What were the motivations for this design?

View on HN

My guess is a combination of the following:

1. Building 3D data is too large or inconvenient to store on the device.

2. Continuously downloading/caching small localized chunks of that data would result in unacceptable use of bandwidth for customers with limited data plans.

3. Their implementation of the algorithm may be CPU inefficient and contribute to excessive battery drain.

4. (cynical) This gives them yet another excuse to be sucking up and storing 1Hz precise user location data, potentially to use for other reasons...

Reply on news.ycombinator.com