@joncox, The integration of the cheap joystick looks great! The recess gives a nice method of glueing in the rubber. I will definitely try that some time!

If I may make a suggestion:
BarButtons uses a schema to combine multiple buttons to less pins. Your design needs a full pin for each button. BarButtons programming design allows for additional buttons. I am thinking:

separate volume buttons a button to easily switch between a navigation or a media keymap a Push-To-Talk button for Zello or likewise apps

This is especially useful since the joystick leaves a lot of space for additional keys 😉

@Corjan-Meijerink, okay thanks. Does the speedometer indeed say 0 km/h in such a case of extrapolated location?

@Emmanuel-Katto, just click and drag on the map 😉
These links will be helpful:

https://support.myrouteapp.com/en/support/solutions/articles/12000096397-manual-create-a-new-route-

https://www.youtube.com/@Myrouteappforyou/streams

@Corjan-Meijerink komt de taal optie in de release van 17 oktober op Android?

@Leike-Lodiers, Shaping points will be auto-skipped, if that feature is enabled in the settings menu. It is the VIA points (hand symbol) that will not be skipped automatically, not the shaping points. It can take up to 3 recalculations before a shaping point is skipped automatically. The app assumes that you will want your meticulously planned route to be driven as planned 😉

@Corjan-Meijerink love it, "just yet" means it's in the pipeline. This option will be a great help for when there's no coverage.

I use my old phone to navigate so I don't have a sim in it nor data.

@Marco-7v hoi Marco
Heeft te maken met de instellingen. Moet zijn kortste weg en profiel auto

@Dae-0, yes, I agree with that.

And even without detailed info, the exit number will be displayed 🙂
eg. "Take exit 4"

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

@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.

@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.

@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.

@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.

@Hubert-Thoring yes, I'd seen your phone cable which is certainly an option to put gpx1.2 to the XT2. And as you've seen, it has to be Tread otherwise. I'm actually happy with gpx1.1 if I can manage to get it right all the time.

The issue most of us seem to be having is Tread getting hold of our pre-built routes and changing them should we not have enough shaping points. I've tried using the MRA 'expand' option but yet again, not usually compatible with Tread, I think due to the random nature of where it places the points. So it's a case of manual input of a limited amount of shaping points in order to try to stop Tread thinking better. I think any more than 50 per route and it also goes tilt and will not calculate.

It's a different beast this XT2 but I love MRA and want to keep using it. The Tread planning function is a half decent compromise on the move to plot a diversion etc. but definitely nowhere near as good.

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.

screen885.jpg

Der wird aktuell beim Start der Navigation angezeigt.

Ein weiteres Beispiel:

screen887.jpg

Die Baustelle am Dreieck-Düsseldorf-Süd wird schon bei der Planung umfahren.

screen886.jpg

Also in dem Bereich alles korrekt.

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

b454b683-c0a8-444e-a8a1-a6ea10ea396e-image.png

Interesting photo of CarPlay and a tablet.