Anyone involved in software is either a user or a developer.
To the developer, the user is the person who simply doesn’t understand their brilliant ideas and then gets everything wrong.
To the user, the developer is the person who comes up with great things that nobody needs and that often don’t even work.
In user-centred development, such as myrouteapp, the developer tries to meet the user’s needs.
This leads to more and more features being implemented.
This results in a growing number of parameters in the programme, the significance of which is often not sufficiently considered and which are frequently used incorrectly.
And even if everything runs smoothly at this level, the map provider steps in and provides inaccurate data, which in turn leads to unexpected changes to the route.
The Google type enters a destination and expects the sat-nav to take them there. They don’t want to think, they just want to arrive.
The myrouteapp type wants to have a pleasant journey and arrive at the end. The journey is the most important thing; the destination is secondary.
Every sat-nav system starts out as Google.
Then there are options to modify the expected route, such as avoiding motorways…
There are various route engines: myrouteapp-Here, TomTom, OSM, Garmin.
These use not only different maps but also route algorithms with different parameters.
MRA stands out because the user/planner can configure these various options themselves.
But in the end, the engine starts up and the sat-nav begins building the route from scratch again. Roadworks, road closures and accidents are taken into account. And suddenly I’m driving round the mountain on the left rather than the right.
The only option is to plan the route yourself so that you get where you want to go.
This must then take into account the various maps, route algorithms and known road closures, etc.
For a 3,500 km journey through the Alps, I expect a driving time of over 70 hours.
On my trips, the time spent on preparation and planning always exceeds the actual driving time.
You felt being called an idiot; that had something to do with the defaults.
There are no defaults in MRA; you get those from Google.
There’s your planning, and then in the navigation app there are presets that are appropriate for your situation and, above all, for your style of planning.
Unfortunately, that takes work – many hours…
This work can be made easier, because there are many experienced people in this forum who have already planned exactly this kind of journey.
But they’re not keen on helping someone who thinks they’ve already done everything right and then complains. Sorry about that.
Once you’ve started your planning, feel free to post it here, and there’ll definitely be people here who’ll take a look and help you.
This is a forum for enthusiasts who are passionate about the subject.
And it’s a forum that developers read too. That’s the only way MRA could have become so excellent.
And if something doesn’t work, be honest enough to consider that perhaps you caused it, rather than a bug in the software.
That’s how MRA and Next have become what they are today. Help make it even better.
RT
I’m known for plastering the whole screen with stuff, but you started it… :-))
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined