Feature Request: Map Contrast & Road Visibility in Navigation⁠

[Rezzonico Mauro]

Subject: Feature Request: Map Contrast & Road Visibility in Navigation
Hi MyRoute-app Team,
As a lifetime subscriber who uses the Web Routeplanner regularly, I’d like to share a suggestion to improve map readability while riding.
The Issue:
While the active navigation track is clear, the surrounding secondary roads, street names, and map details are far too thin, faint, and low-contrast.
Why it Matters:
When riding a motorcycle, quick readability is essential. It is crucial to clearly see the surrounding road network at a glance, not just the blue track line.
Proposed Solution:
Add an option for High Contrast / Bold Roads map style.
Increase line thickness and contrast for secondary roads.
Improve font size and visibility for street names.
I have attached a side-by-side visual comparison to illustrate the difference.
Thank you for your continuous work on MRA!
Best regards

[LennyO]

I am all in for better contrast, but I would like it slightly different then yours, which makes the map way too busy for my taste.
Personally I would appreciate a little more contrast for roads and more than that for street names and such.

[Rezzonico Mauro]

@LennyO
Thanks for the feedback Lenny! My image was just an exaggerated visual example to clearly highlight the contrast issue. Having customizable display settings—or a subtle balance like you described—would indeed be the perfect solution so everyone can adjust it to their taste.

[Guzzist]

I fully agree! And it is discussed in other threads too.
I drive a lot in all weather conditions the whole year and it's often annoying to have a white (or light grey) screen and white roads on it. So, it's not helpful for such map style, to have a screen with 3000 NITS; white is white.

I know it would be not easy to find a color scheme, which fits for all users. Therefore I often suggested: the configuration of the color scheme should be kept in a txt file of the app. If users with passion want to optimise it for own needs, they can override the #hex code for some colours.
That's not difficult for users and there is no risk.
Garmin is doing it for Zŭmo models.

[Stevedo 6 0]

I agree with all the sentiments that this needs to be addressed.

I think the best way to address this is not via a txt file but by a number of profiles that can be configured by the end user. These profiles would be configured in the online planner and synchronised to the app for navigation. The end user can then select the most appropriate profile for their current situation.

So for example, I might configure a profile for use on my bike where I use a ruggedised phone for navigation. In my car I have a built-in Android Auto/Carplay device which would use a different profile. For my camper I have a different set of requirements and therefore a different profile. The key is that I as the end user can define, easily save and then select the best profile for my scenario.

Settings would include, but certainly not limited to: map colours, road colours, contrast, route colour, line width and opacity, map scaling, zoom level at which POI's appear (by category), etc etc.

This way you can set a "sensible" default that can be used, probably by a majority of users, but also give "power" users the opportunity to customise their navigation experience.

We all use different devices in different environments, some are colour blind or have other visual impairments and others have very strong preferences. The development team will never be able to accommodate all of these scenarios so give the end user the option to choose.