3 ms·
Tough to say in the general case, but it's often a good idea to adhere to the so-called "principle of least surprise" in UX design. If I'm riding on a trail th
by CamperBob2 11y ago
Tough to say in the general case, but it's often a good idea to adhere to the so-called "principle of least surprise" in UX design. If I'm riding on a trail that periodically approaches and diverges from a nearby highway, which is common around here (Seattle area), I don't want my recorded path to snap to the highway every time I exceed 12 MPH. That would come as a surprise -- an unpleasant one. I'll go so far as to say that nobody would ever expect this to happen, or be dismayed if it didn't.
That's a good reason not to include a given feature, or at least to allow it to be turned off. Someone at Apple obviously thought it was a good idea, but they clearly didn't ask very many other people, or ask any cyclists at all.