The backend at this point is just Graphhopper so I think it would make more sense to use it directly and customize it based on your needs: https://github.com/graphhopper/graphhopper

Oh man, that's sweet! Thank you. I would be at your door by now but I'm located 8000 km away from Oregon :D I just received a tiny M920Q, and 64 GB of RAM should arrive tomorrow. I'll have to make do with it for now :D

Thank you! I'm a total Java noob - actually, this is the first project where I've written any Java code (had to slightly modify the Graphhopper source code to suit my needs). Those libraries look very interesting. I'm saving this post for another battle with processing maany GBs of OSM data :D

Thank you! I didn’t add a way for people from other regions to sign up, like a newsletter since I figured most people dislike it here on HN. You can check back on this thread in 2–3 weeks, and there should be an update comment from me announcing a new version of the planner with the US region included.

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.