3 ms·
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
by ryandrake 8y ago
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...