Na 5000km MyRoute-app: helemaal klaar met deze Bugware

[ATLast]

I understand your frustration—I've had my share of problems with the app in the past, see my posts in this forum—but I think your opinion, probably written in the heat of the moment, is a bit excessive: the program has indeed improved significantly.

I also notice that we probably use it in the same way—as a route planner from point A to point B—and that doesn't seem to be how most users use it. When I go on a trip, I don't plan the whole trip on the website but set a destination for the end of the day and let the program do its job. I want the flexibility to visit places that aren't on the itinerary but that I find appealing.

This requires recalculating the route, which is still not the app's strong point, even though it has also improved considerably, thanks to the developers.

And the recalculation problem is amplified when the internet connection is weak or nonexistent: unfortunately, it's often impossible to change this while driving because you don't always notice it, and it's not always easy to stop and switch to offline mode. From my past experience—though I haven't tried this in a while I must say—offline mode has never helped me; otherwise, I would always travel "offline." For your information: I download maps of all of Europe and take care to keep them up to date.

I adjusted the route calculation by enabling all the avoidance options, which the app seems to handle less well than before: I too have been sent onto a highway, through a village to avoid 400 meters of main road, or via a parking lot… I also find that here in Belgium, the program makes much less effective use of smaller roads than in version 4: there are also fewer winding road options (3) than before (5). And the difference between level 2 and level 3 is, most of the time, imperceptible.

A few weeks ago, I took a 2200 km trip in France, and the app worked very well: almost no crashes, and I was able to cross France to and from the Dordogne region with very few two-lane roads. This might even require extra attention because, in rural France, there are very few places to refuel.

Did you specify what type of phone, system, and Android Auto/CarPlay connection you're using? It can also affect how the app works or behaves.

As for me, and I've been a user since version 1 of the program, I'm confident that with a little more patience, the app will have eliminated the biggest flaws that sometimes affect my journeys. I don't just use it when traveling, but also in Belgium: I've already discovered many places that were previously hidden from me.

I've already tried other apps: OSMand, Calimoto, etc., but none of them appealed to me because they all offer far fewer features than MRA. And while it's true that the menus are sometimes unclear, with practice you get the hang of it. It's also important to remember that the complexity of navigating the menus is partly due to the sheer number of options available.

In any case, if you find an app with as many features that works better, please let me know.

Ride safe.

[Marinus van Deudekom]

Most of the problems start with users that use CP & AA. Do you use one of them.
If that's not the case Create the logfiles by long pressing in the version number and send them with a ticket so the devs van have a look at it.
If you are using CP & AA, it one of them. Some users dont experiance problems, me for instance, and others do. Depending on their configuration of is minor of major.

[M. Schrijver]

Had just a frustrated experience. It was a sum of things. Not all can be lead back to MRA. But the behaviour of MRA frustrated me the most

Currently I'm on holiday in Ireland. That means little knowledge how the traffic flow in Ierland is build . I was on the M4 heading Dublin. The idea was straight through Dublin. It was a pre-planned route with multiple points in Dublin. But because the directions MRA gave me and the lack of knowledge of the road structure. I landed on the M50. This was my starting point of my frustration. And once on the wrong highway. Turning back is not an option. But the recalculation tries to go back to the missed waypoint. Which is normal for MRA. But not logical in this situation. After some more wrong turns (also partially because of the given directions) and keep sending back to the missed waypoint (point 5). I was almost boiling of frustration. Finally I found a place to stop the bike and look at the route. Skipping to point 13 was the most logic thing to do to get back on the route.

MRA is a good tool but there are situations where things are getting meshed up pretty well.
Just like some other postings tell. MRA is good but not flexible enough. At least that is my opinion.