4 ms·
Hmmm. Well, the "places of interest" it suggested to me didn't look interesting, but it's nearly useful. What it really needs is just to have a "time" column es
by hugh3 15y ago
Hmmm. Well, the "places of interest" it suggested to me didn't look interesting, but it's nearly useful. What it really needs is just to have a "time" column estimating how far each stop is from the last one.
Maybe I just grew up watching too many NSW RTA ads, but I'm a firm believer in the principle that for safety you should stop and get out of the car every two hours. So if it could suggest stops which were spaced roughly two hours apart, it'd be useful to me.
- daryn 15y agogreat suggestion Hugh. We definitely want to incorporate the time of day and time between stops at some point, both for the reason you suggested as well as to be smarter about the types of attractions we suggest at different times. thanks!
- joesunga 15y agoThat's funny you say that. The "time" situation was something we struggled with to find what the best experience would be. The questions we had were: - Do you stop 1 hour all the time when you stop at a restaurant? What if you take it to-go? - What if you stop at a stop like the World's Largest Frying Pan for just 5 minutes? Should we allow users to add custom time limits for each of the stops? - Would we be complicating things adding custom times? All great questions and things for us to think about. Thanks a ton for the feedback.
- hugh3 15y agoI'd only want an estimate of the travel times between destinations, not an estimate of how long I'd actually spend stopped at each (which I wouldn't attempt to estimate in advance anyway). For me the use case is this: I want to drive from (say) San Francisco to Denver, and want to plan out a schedule which involves stopping every two hours for a break.
- joesunga 15y agoAhhh...got it. Thanks for clarifying that.