I'm relatively new to Beeline, and so far I'd describe my experiences with it as pretty frustrating. I'm hopeful that better calibration will fix the errant arrow pointing, but one issue is particularly annoying:
Why is there no cross-checking in the app between the direction of the arrow and the distance to the waypoint?
The classic example of this, which I've had a few times now, is that the arrow will be pointing anywhere but forward, while the distance to waypoint steadily reduces (because the arrow is pointing the wrong way). Just this evening in fact, I cycled 1 km down a Roman road i.e. an entirely straight road. The distance to the waypoint reduced consistently, but for the entire time, the arrow pointed to the left, when in fact my destination was a house on the same road.
That's frustrating in itself, but it begs the questions: how is this even possible? Why doesn't the beeline device and app check for some kind of correlation between the direction that the arrow points and whether the distance to the waypoint is going up or down? How can the Beeline app be okay with the distances to each successive waypoint counting down faithfully, while the arrow points anywhere but the right direction? Why isn't Beeline checking for such illogical outcomes and coming up with a helpful error message (e.g. "Re-calibrate") or at the very least acknowledging the error to the user and telling him/her that details of the error is being sent to the app developers?
Looking forward to your response.
Please sign in to leave a comment.