Navigation mode UI/UX improvements (excluding CarPlay and Android Auto)

[biodranik]

Let's collect here all user-interface improvements for both platforms, and reference all existing issues.

• Next turn street's name occupies a lot of space in landscape navigation #2177
• Landscape mode: use the left and(or) right space for the info bar and buttons
• Show current street name
• Show the street/link/exit number/name for the next turn Navigation: show the street/road/exit name for the next turn #849 and include street names in voice guidance #615
• Show current speed
• Show turns ahead Add a feature to show turns ahead #1320
• Use larger font size for texts
• Improve dark mode Synchronize night mode to phone system settings (Android + Android Auto) #749
• Make bottom bar texts larger and more visible
• Navigation mode is not restored when the app is closed/killed. The route preview is restored instead on both platforms.
• Avoid XXX route options are not always visible in the route preview
• Manage route (reorder stops) is not implemented on Android
• Announce street names include street names in voice guidance #615
• Announce roundabout exits in advance to have time to choose a right lane
• Sometimes shops are not displayed while navigating by bicycle
• Show "route overview" button while navigating
• "North up" mode is not saved after dragging the map and centering it again North up" mode is not saved after dragging the map and centering it again #1461
• Save viewport rotation setting (north on top/drivers perspective) #1691
• Improve perspective view #2055
• Pedestrian navigation improvements including compass rotations #2056
• Increase the font size for the roundabout exit number in navigation mode #2198
• Smart zoom-in and zoom-out in navigation mode #2395
• Tap on the direction arrow repeats the last voice direction (one user told that he wants it for cycling and walking navigation)
• Show private roads differently or ask a confirmation from user to navigate there

[TimMagee]

Is this issue for visual improvements only? There is also #615 for including the street names in voice guidance.

[biodranik]

The idea is to collect many scattered but related issues into the one for reference, to understand the whole picture.

[john-p-williams]

I'm using the latest f-droid version, and I've found navigation unusable here in England, because the voice prompts do not announce which exit to take from a roundabout in advance. There are very many roundabouts here and it is essential to be in the correct lane when approaching a roundabout, depending on which exit you want. But the voice prompt waits until you reach the roundabout before announcing the exit number; by which time it is too late.

[Donkey-Doug]

New issues: #1401, #1402, #1404, #1407, #1408, #1409, #1410, #1411

[arnaudvergnet]

Here are some other ideas:

• Show intermediate steps time and distance. It could be shown in a list in the navigation menu.
• Quick access to route options. Right now we have to click on the settings icon then scroll to the navigation section to open the Routing options.
• Show elevation data with current position. Elevation data is only shown on route calculation for cycling and pedestrian modes. It would be nice to have access to this information while navigating by opening the navigation menu, in a progress bar style to see our position.
• Show speed limit.
• Show road sections with a toll in a different color while rendering the route. We have icons indicating passage in a toll booth, but coloring the actual section would make it easier to understand how much it will cost. Displaying the number of kilometers under toll would also be great.
• Show route code in priority over route name for larger roads (highway, motorways, primary roads, etc). This is useful in car navigation because road signs often show the code instead of the name in directions (at least in France).
• Improve motorway exit rendering. These are very useful in France but they are shown in plain text with a low priority, forcing the user to zoom very close to read the exit number.

[alensiljak]

Hi! Been trying to use OM for car navigation. There are some excellent positive traits (the route is great, zoom in/out is fantastic, etc.) but here I'll focus on the missing bits. Please review and/or add to the list above.

• Show the speed limit. This one is a blocker for me as there are plenty of residential (30 km/h) zones around that intersect standard (50 km/h) roads. Seeing the current limit helps a lot. Edit: The speed limit warning (the red background on the speed indicator) actually works but only sometimes. Not sure what triggers it on/off.
• Improve the time estimates. I would not achieve the current ones even if I could fly. Some obvious factors, like traffic lights and turns, should apply some coefficient. I.e. there's a chance of hitting a red light and adding 1/2 a minute to the time; turning at a 90 degrees angle involves slowing down and accelerating, not traveling at the max. allowed speed, going over pedestrian crossing in an urban area involves a possibility of waiting for pedestrians (sometimes for what it seems an infinite time)... Edit: This one can get used to. The estimates are not that off.
• show speed cameras. Edit: The cameras are there and the notifications and the visual representation is quite ok. The issue is that some cameras don't trigger the warning (they stay black) and some are not on the map. I suspect a data issue and will check the cases I remember on OSM. The problem, as always, is marking these on the spot (while driving) or remembering where exactly the camera was, to look up at a later time.
  Edit: Here is a camera that is not recognised: https://www.openstreetmap.org/edit#map=19/48.24141/16.37253
• show exit signs / shields more prominently on screen instead of just a text line with the name
• show which lanes to use at the next action point (i.e. stay in the left two lanes). Edit: This is probably Lane assist #1404
• visually represent the roundabout exit. I'm a visual person and "take the second exit" doesn't mean anything to me if I'm looking at the traffic ahead. My brain literally does not register what that means. Seeing an image of a roundabout where the route is depicted helps immensely, on the other hand. Edit: This is also ok as the roundabout is already on the map.
• customizable route - i.e. add waypoints / intermediate stops. Edit: ahh, thanks! Did not notice that there is that option already. Sorry!
• "turn right then turn right" instruction should add the distance until the next action. This always sounds like I need to turn twice right away. "Turn right then, in 150 meters, turn right" would be much better.

[biodranik]

@mistery you can already select any point on the map and "Add stop" (add a waypoint).

[thegrasshopper104]

• Don't show house numbers when the destination is >1km away. Displaying house numbers in a dense area really clutters the map and adds no benefit to navigation.
  

[Esmolante]

In #3981 I suggest adding the altitude and distance to the next stage at the bottom of the panel, in line with the ETA.

In addition, it may be useful to add a compass to indicate the direction in which we are moving.

And a small detail: in continental Europe, as well as in most of the world, the decimal separator is a comma.

https://en.wikipedia.org/wiki/Decimal_separator#/media/File:DecimalSeparator.svg

[biodranik]

@Esmolante thanks! Can you please create a separate issue for wrong decimal separators which are different from your phone's locale/language?

[rtsisyk]

What is the purpose of this grand ticket? Would it be possible we create individual tickets instead? Labels are very useful for organizing tickets by the domain.

CC: @oleg-PK

[rtsisyk]

What is the purpose of this grand ticket? Would it be possible we create individual tickets instead? Labels are very useful for organizing tickets by the domain.

CC: @oleg-PK

[oleg-rswll]

If there is a plan to implement all the issues which are listed here, instead of this issue there should be a Milestone, and the issues are added to the milestone.

If this issue is just about identifying open issue relating to Navigation Mode, then there should be a label called "Navigation Mode" and all the issues labeled with it.

[biodranik]

The initial goal was to collect feedback in one place, to overview the whole picture, and then to create separate detailed issues.