[serf]

>I'm an android user, and it kind of shows a blue "cone of uncertainty" when it isn't sure which way its pointing, and occasionally asks either to move the phone in a figure of eight or to point at nearby building to calibrate.

Apple products and animations generally have more smoothing and hysteresis; my presumption is that the accuracy is hidden from the user in an effort to make sure that the arrow doesn't fluctuate wildly, whereas the android UI is more likely to show artifacts from the 'noisy' GPS/IMU fusion and inherent magnetometer inaccuracies.

'Slow arrow' was one of the things that kind of drove me crazy in iOS back in the old days now with faster hardware I notice the 'twitchy' arrow more on other platforms.

tl;dr: Most modern hardware is pretty equal as far as being able to determine its' place in space and time with decent accuracy now , but not all navi software is equal in terms of dead reckoning accuracy and pose estimation given the current data and the user expectation of noise filtering while handling the phone.