Disclaimer - my site. It’s very focused on quiet routes, so will generally prefer a hilly road if the alternative is a traffic-infested one. Europe/North America/AU+NZ only at present.
UX observation: clicking to create a start and end was relatively intuitive, but it took a while to find "Close route" to reset it (and be able to click for start / end points once more).
How do you determine quiet-ness? Is it just by the grade of the road, or do you have some kind of data feed for quietitude?
E.g. in the UK, some A-roads can be very quiet despite being technically major, whereas some B-roads or even ungraded can be very busy, e.g. if they are used as shortcuts.
My workflow is 3 monitor setup. Komoot in the middle, actually planning the route. Strava heatmap on the left to see where people often travel in an area. Gmaps on the right to see streets and street view.
It's still a pain to plan, but it's _so much easier_ with komoot.
No.
Google Maps directions for bikes is a good start but you have to take the routes with a big grain of salt (even with that Google is still better than every other app I've tried). I street view the route to make sure there's a least a good shoulder and re-route appropriately.
Used by ultra-racers to plan multi-day events.
My only problem is, that when I select 'road ride', it tries to get me on a bike path. That would be a good thing for some people.
Even for route planning (years ago) which I would not say Strava is fantastic at, it still seemed worse.
YMMV