Thanks for the reply.
I guess my take from what you've just said is that it is the Route Navigation algorithms which make up the journey time in the Itinerary, not the Myroute app and thus it would be difficult to implement I get that.
I would dispute the too many variables to be useful comment.
Bear in mind that I'm not talking about dynamic timings whilst riding most Nav apps are pretty good at ETA's and you learn with experience
I'm talking about what is, for me at least, one of the primary differentiators of MRA. Ease of Route Planning for use on a variety of devices.
Its the easiest to use and most versatile route creation tool I've found, by a country mile.
I would argue that for route planning and producing an itinerary these variables, think Fuel stops, Photo Opportunities, Cafes, Restaurants, Museums Etc take up a significant part of the day, especially with a large group or a "sightseeing" type of trip. Route planning without taking these variables into account only produces a useless itinerary!.
The current process is iterative - create a rough route and planed stops. Manually allow for the variables above, realise that the planned stops don't work together. Modify the route and/or or stops, recalculate. Repeat until we have a route that arrives at museums when they are open, and planned food breaks and final destination at about the "right" time.
If MRA used the journey time data from the nav app but enabled users to allow for these waypoint variables to produce a detailed Itinerary with modified timings when creating the route, it would significantly simplify this process, and produce a reasonable itinerary first time every time. I would consider that to be useful to me and presumably others too.