Navigation UX is confusing / does not make all possibilities apparent #10348

Open
opened 2025-02-26 12:01:03 +00:00 by bocops · 0 comments
bocops commented 2025-02-26 12:01:03 +00:00 (Migrated from github.com)

Problem:

As a first-time user of the Android app, it took me several attempts to eventually understand the navigation UX, failing at different steps along the way:

  1. When navigating, I typically select the destination first, by either tapping on the map or searching. Either way, I end up with buttons "Route from" and "Route to" shown for the chosen POI (let's call this D).
  2. Tapping "Route to" immediately starts a navigation from my current location to D, even if I intended to pick a different starting point.
  3. Tapping "Route from" instead displays text "Use search or tap on the map to add a destination point" - but doing either does not actually "add [the] destination point". Instead, it shows buttons "Route from" and "Route to" again. I initially did not expect having to tap on either.
  4. At this point, tapping "Route from" discards the previously selected point.
  5. Only if instead tapping "Route to" (point S), I end up with a navigation between the two points I want to navigate between - but even then, they are in the wrong order (D to S instead of S to D).

In summary, the only apparent way to start a "correct" navigation between arbitrary points seems to be:

  1. Select starting point, tap "Route from"
  2. Select destination point, tap "Route to"

Only just now, while writing this issue, it occurred to me that I can also:

  1. Select destination point, tap "Route to"
  2. After navigation from current location is already being displayed, tap starting point, select "Route from"

Obviously, none of this is wrong per se, but perhaps the different possibilities could be better hinted at in the UI.

Potential enhancement:

  • Clarify in the UI that:

    • stops can be added after a navigation has already started (solving item 2 and the "Only just now" part)
    • destination must be added via "Route to" button (solving item 3)
    • tapping "Route from" after starting point has already been selected replaces point (solving item 4)
  • Additionally, allow reversal of a navigation (Start <--> Destination) to solve item 5

  • Alternatively: For the first stop selected, get rid of the "Route to/from" differentiation, replacing these actions with a single "Navigate" button. If this button is tapped, bring up the following different options:

    • "Route from current" (interpreting selected stop as destination, navigate there from current location)
    • "Route from ..." (interpreting selected stop as destination, allow picking a starting point)
    • "Route to ..." (interpreting selected stop as start, allow picking a destination point)
**Problem:** As a first-time user of the Android app, it took me several attempts to eventually understand the navigation UX, failing at different steps along the way: 1. When navigating, I typically select the destination first, by either tapping on the map or searching. Either way, I end up with buttons "Route from" and "Route to" shown for the chosen POI (let's call this D). 2. Tapping "Route to" immediately starts a navigation from my current location to D, even if I intended to pick a different starting point. 3. Tapping "Route from" instead displays text "Use search or tap on the map to add a destination point" - but doing either does not actually "add [the] destination point". Instead, it shows buttons "Route from" and "Route to" again. I initially did not expect having to tap on either. 4. At this point, tapping "Route from" discards the previously selected point. 5. Only if instead tapping "Route to" (point S), I end up with a navigation between the two points I want to navigate between - but even then, they are in the wrong order (D to S instead of S to D). In summary, the only apparent way to start a "correct" navigation between arbitrary points seems to be: 1. Select starting point, tap "Route from" 2. Select destination point, tap "Route to" Only just now, while writing this issue, it occurred to me that I can also: 1. Select destination point, tap "Route to" 2. After navigation from current location is already being displayed, tap starting point, select "Route from" Obviously, none of this is wrong per se, but perhaps the different possibilities could be better hinted at in the UI. **Potential enhancement:** - Clarify in the UI that: - stops can be added after a navigation has already started (solving item 2 and the "Only just now" part) - destination must be added via "Route to" button (solving item 3) - tapping "Route from" after starting point has already been selected replaces point (solving item 4) - Additionally, allow reversal of a navigation (Start <--> Destination) to solve item 5 - Alternatively: For the first stop selected, get rid of the "Route to/from" differentiation, replacing these actions with a single "Navigate" button. If this button is tapped, bring up the following different options: - "Route from current" (interpreting selected stop as destination, navigate there from current location) - "Route from ..." (interpreting selected stop as destination, allow picking a starting point) - "Route to ..." (interpreting selected stop as start, allow picking a destination point)
This repo is archived. You cannot comment on issues.
No labels
Accessibility
Accessibility
Address
Address
Android
Android
Android Auto
Android Auto
Android Automotive (AAOS)
Android Automotive (AAOS)
API
API
AppGallery
AppGallery
AppStore
AppStore
Battery and Performance
Battery and Performance
Blocker
Blocker
Bookmarks and Tracks
Bookmarks and Tracks
Borders
Borders
Bug
Bug
Build
Build
CarPlay
CarPlay
Classificator
Classificator
Community
Community
Core
Core
CrashReports
CrashReports
Cycling
Cycling
Desktop
Desktop
DevEx
DevEx
DevOps
DevOps
dev_sandbox
dev_sandbox
Directions
Directions
Documentation
Documentation
Downloader
Downloader
Drape
Drape
Driving
Driving
Duplicate
Duplicate
Editor
Editor
Elevation
Elevation
Enhancement
Enhancement
Epic
Epic
External Map Datasets
External Map Datasets
F-Droid
F-Droid
Fonts
Fonts
Frequently User Reported
Frequently User Reported
Fund
Fund
Generator
Generator
Good first issue
Good first issue
Google Play
Google Play
GPS
GPS
GSoC
GSoC
iCloud
iCloud
Icons
Icons
iOS
iOS
Legal
Legal
Linux Desktop
Linux Desktop
Linux packaging
Linux packaging
Linux Phone
Linux Phone
Mac OS
Mac OS
Map Data
Map Data
Metro
Metro
Navigation
Navigation
Need Feedback
Need Feedback
Night Mode
Night Mode
NLnet 2024-06-281
NLnet 2024-06-281
No Feature Parity
No Feature Parity
Opening Hours
Opening Hours
Outdoors
Outdoors
POI Info
POI Info
Privacy
Privacy
Public Transport
Public Transport
Raw Idea
Raw Idea
Refactoring
Refactoring
Regional
Regional
Regression
Regression
Releases
Releases
RoboTest
RoboTest
Route Planning
Route Planning
Routing
Routing
Ruler
Ruler
Search
Search
Security
Security
Styles
Styles
Tests
Tests
Track Recording
Track Recording
Translations
Translations
TTS
TTS
UI
UI
UX
UX
Walk Navigation
Walk Navigation
Watches
Watches
Web
Web
Wikipedia
Wikipedia
Windows
Windows
Won't fix
Won't fix
World Map
World Map
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: organicmaps/organicmaps-tmp#10348
No description provided.