You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every once in a while I encounter users who are trying to explore a prospective route from A to B, but then instinctively tap the 'Start' button falsely assuming only that would trigger the route calculation.
They are thrown off by the app now starting a navigation from their current location. (e.g. #20021 (comment))
Maybe a wording change could help mitigate this, like renaming the button to 'Navigate'...
The text was updated successfully, but these errors were encountered:
@dmpr0 I believe the comment resulted exactly from a situation like I describe above, where the user thinks they have to tap the 'Start' button to calculate and be able to investigate the route.
But the A -> B route must be investigated using the 'Details' button, and without tapping 'Start', because the word 'Start' refers to starting a turn-by-turn live navigation, something the user exactly does not want at this point, it seems.
Every once in a while I encounter users who are trying to explore a prospective route from A to B, but then instinctively tap the 'Start' button falsely assuming only that would trigger the route calculation.
They are thrown off by the app now starting a navigation from their current location. (e.g. #20021 (comment))
Maybe a wording change could help mitigate this, like renaming the button to 'Navigate'...
The text was updated successfully, but these errors were encountered: