Interesting assumption. My mind goes to to a) Most people are mobile first and b) In this category of app, i imagine people want the route with them on their phone as they bike (as they're probably unfamiliar with the route, hence the need to plan it)

Cool idea, i'd love to try it but honestly i'd love it on my phone for the aforementioned reasons!

---

Edit: Some follow up remarks (From Chrome on a Mac)

1. I found it a bit confusing when creating a route. I assumed it would let me do address completion. The UI seems to just be naming my route instead, i think if you're going to borrow visually from Google maps you should follow their patterns.

2. I was able to add my first point (my home), but adding a second point never worked.

3. The click mechanic is a bit odd. I expect clicking elsewhere when the menu is open (add point/close) that the menu would go away - rather than re-appear in my new click location.

4. The map centred me over Europe, i'm in Canada however. Some GeoIP lookup here could give a better experience.

5. Re:point 2, this seems to work when i selected random locations in Europe. I assume this is a data issue? So the real issue here (apart from the routing not working) is there's no feedback on the UI when the routing fails.

6. Refreshing my screen loses my route. Any chance you could save it to local storage or something? Would be amazing if i could create this route on my desktop and then send a link to my phone (once mobile is supported?)

I think the purpose is to export the route to GPX, so that you can use it on your phone when you're cycling.

Thanks for the feedback! I actually want to have it on mobile as well but will most likely choose React Native instead of trying to make the web app work on mobile (or maybe only with some very simple functionality). At first, my approach was to have a planner on desktop and route viewer/navigator on mobile, but you're right - there needs to be an option to update/modify your route while traveling.

Regarding state: it's only a matter of changing the blacklist array in redux persist config. Right now I have all global state blacklisted because I noticed a small bug with rendering the map layers when the state is persisted and I didn't have time to fix it but in the next version it will be persisted in localstorage.

>a) Most people are mobile first

I couldn't imagine trying to build a complex route on a tiny screen with a crappy phone UI. I am starting to feel like an old man yelling at clouds here. Why in the hell wouldn't you prefer to use a nice monitor with a mouse for a complex task like this?