Hey guys,
Author here - thanks for the feedback!
Fennec pointed out that the app doesn't process intersections that well. This is because the program uses Google Maps API, and it's not interpreting the address correctly at this moment. I tested with Google Maps and it's able to correctly interpret it (though not always), and so I need to figure out why it's not working through the API. Definitely have added to my fix list though. First step would be to add a map back in and see where it's pointing to!
As far as the [object object] error, I've definitely noticed this as well. There's probably a way within Google Maps API to handle this, because it doesn't happen when you use Google Maps, but I haven't found it yet.
morbiuswilters pointed out that the time estimates are optimistic. I definitely agree - I even mention this on the Methodology page. The estimate is provided by Google Maps and seems bullish. I want to add a drag factor, but I need to work out how to ask the user for data after their trip. Any suggestions?
And of course, the server crash. I had no idea I'd get that many hits from Hacker News, and now that I see there's at least a fair amount of interest, I need to find a better webserver. Are there any servers this group would suggest?
All in all, definitely a beta and thank you for taking a look, though I'm cool calling it an alpha as well! As I pointed out on Hacker News, this is my first program in a decade or so. No boot camp, just learning on my own. All constructive feedback as I learn is much appreciated :).
[Added <br>'s because Community Server is horrid. -TheShadowMod]