I tend to agree with @Simon-q having the point name in any popup/notification would be a lot more informative than just a number. Distinguishing between via & shaping points in this regard is IMO a nonsense, they are all points & should be treated the same, making a distinction just adds useless complexity. What I also think would be useful & might make the numbers a bit more meaningful is if the option to "Show Next Waypoint Information" actually did what it says. [image: 1731440728236-f4f3cb37-bf53-46ce-9956-a614892e16c0-image.png] At present I believe this option only shows the point information when within a certain distance of the point. If the point name was shown immediately after the previous point was passed, then the user would have time & maybe able to associate this point name with the number on the waypoint/skip button. If the user selects to see the next point name show it to them, don't hide it with some hidden filter. IMO this is a poor design choice.

@Simon-q it’s the limitations provided by Google and Apple are the cause that some features that you can use on a smartphone can’t be used on the screen of CarPlay an Android Auto

@Rob-z fixed now if you update the app to the latest version. [image: 1731262436247-screenshot_20241110_200423.png]

@Rob-z have you updated to the lasted version of the app ? This is how it looks for me with line width of 0.50x [image: 1731262002674-screenshot_20241110_200423.png] [image: 1731262012689-screenshot_20241110_200431.png]

@Josep-Lluis-Rodriguez-jlrdelc Vaya a su cuenta y desplácese hacia abajo. Allí podrás ver tu suscripción. [image: 1731075543577-img_7005.jpeg]

@Jörgen Agree with you and I like it.

@RetiredWingMan said in Changing the size of the displayed speed limits: @Peter-Levis personally I like the current sizes. I don't want the entire screen taken up by symbols etc. The purpose of the navigation software to to show a planned route on a clear easy to read map. I have a speedo and I can read speed limit signs on the side of the road. I too have a speedo and can read road signs but my point is a UI that is user defined to take into account the screen size you are using. On my iphone XR the UI elements could be a little bigger and there would still be plenty of map to see. However someone using a bigger phone could have those elements bigger and still see the map. Up to the individual.

@Sanktjohanser Hatte heute auch das Problem einer Sperrung auf der Route. Hab den nächsten Wegpunkt einfach übersprungen und bin der Umleitung gefolgt. So geht das auch ganz gut.

@Tegel-Werner, das ist auch ein guter Weg. Danke für den Tipp. Mit den zwei Apple Geräten hast du natürlich den Vorteil der iCloud und den Foto Sync. So das beim speichern des Tracks die Fotos von deinen Aufnahmen zur Verfügung stehen. Bei mir funktioniert das so leider nicht da ich mit meinen iPhone zwar die Fotos mache aber über meinen RT3 (Android) navigiere und somit beim beenden der Route die Fotos nicht auf dem Gerät zur Verfügung habe. Daher dachte ich mir eben ob es nicht so eine Möglichkeit gebe um im Nachhinein den Track mit den Bilder zu bestücken und dabei die geodaten auszuwerten. Das hätte den Vorteil das es Geräte übergreifend funktionieren kann. Vielleicht liest @Corjan-Meijerink das und findet es auch interessant 🤭 Einen schönen Gruß aus Erding ins schöne Ulm Michi

@Roger-Needham-0 When you’re using the web route planner, you can use the upload option in Route lab to add the routes directly to your library, so there’s no need for a download folder. Save the routes from Outlook then upload them to your library.

@Rob-Verhoeff Thanks Rob. Let me give it a shot.

[image: 1729873178372-b454b683-c0a8-444e-a8a1-a6ea10ea396e-image.png] Interesting photo of CarPlay and a tablet.

@Tuxi, see: https://forum.myrouteapp.com/post/56221

Moin, im Allgemeinen funktioniert das ganz gut. Die großen Behinderungen sind meisten drin. Die eine oder andere Baustelle oder Sperrung fehlt schon mal, oder ist schon erledigt, aber wird noch angezeigt. So ganz akkurat und Zeitgenau ist es nicht immer. Es muss ja irgendwie in die Here Kartendaten implementiert, bzw. aktuallisiert werden. Ich habe gerade mal den Stau an der Südbrücke in Dusseldorf angeschaut und mit Google verglichen. [image: 1729669176056-screen885.jpg] Der wird aktuell beim Start der Navigation angezeigt. Ein weiteres Beispiel: [image: 1729669227506-screen887.jpg] Die Baustelle am Dreieck-Düsseldorf-Süd wird schon bei der Planung umfahren. [image: 1729669283954-screen886.jpg] Also in dem Bereich alles korrekt.

@Marinus-van-Deudekom said in Dangerous/difficult curves: @Peter-Levis there you go. I consider all curves and bents not dangerous. The only thing dangerous over there is the driver Quite true - the rider needs to be wide awake, looking, thinking. Calimoto might give you a little extra information - not a lot - but at the cost of looking ahead. There are plenty things that Calimoto won't tell you: the road surface (potholes, gravel, mud, shiny, oil, diesel, leaves) the weather (rain, frost, ice, lying water/blocked gutter) the oncoming driver (who is also looking down at Calimoto as he crosses the centre line ) the tractor that is just out of sight round the corner, but you saw the open farm gate, right? Calimoto didn't.

@riccardo-brizzi, the app already is AAA compatible We already do have live traffic info, and also speed camera warnings That being said, the live traffic does not update dynamically, that is being worked on. And the HERE camera information will never be as accurate as services like Flitsmeister or Google.

@Con-Hennekens said in New User Observations: @richtea999 said in New User Observations: unless users like Peter say what works for them and what doesn't the product quality won't improve. Yes, by no means I meant to discharge @Peter-Levis his input. If the screen-estate can be found to enlarge the font, I am all for it. I just wanted to refute the comment on how easy it is . There are so many parameters to factor in. And even then some people will want an even bigger font No offence taken. I totally get that all devices have to be taken into account but I'm sure the developers have a bank of test devices. I am presuming that the app is written in a modern object language where the UI is separate from the engine. I have an interest in programming and have dabbled in languages such as Flutter and in the past Basic, C, C++ Delphi and even Pythonista on my phone. In those languages it is indeed very easy to test an increase in font size. It does not have to be as large as the road text but maybe just one or two font sizes up. It just needs a tweak. I'm sure the developers are busy on many other projects but I hope they keep their eye on the main objective that the app is used for navigating on a motorcycle with or without voice commands. As you say it is what it is. Just an observation from someone who is interested in UI design.

@PritVader This is something we wish to combine with the development of the new website! High priority for that environment but a long duration till this will be implemented.

@Stuart-McIntosh Best to contact support about this. Personal information won't be discussed on the (public) forum by MRA employees.