38 karma · joined November 29, 2016
But here come their restrictions. Google Maps don't route many waypoints. HERE WeGo don't know places names, often around Alice Springs.
We did not design UI at all, because we are thinking of voice interface. You are telling your desires and constraints in conversation. They are captured. Then API is called.
But here is the real deal - we are going to navigate and move people by any multi-modal transportation. Uber or Moovit or Rome2Rio. First: they could be safe by design. Second: their value proposition is wider. We just started with cars and road trips. Third: car driving will be experience itself in long term future. People will pay to drive like they pay today for horses. People will kiss and lick cool cars.
We have a version in the lab, where you could define durations in locations (e.g. 2 days at Wagga Wagga), even pin location to specific date.
We keep it simple intentionally. Can plug any knowledge graph of POIs and experiences, any rooms and homes, and multi-modal transportation (not only car).
So far togglers are only for you. If you booked smth, you mark it for yourself.
We used to link cities, towns, national parks to Wikivoyage (same content as Wikitravel, but without ads). All POIs within populated places linked to Wikipedia.
You are right about visuals. Totally. I don't know where to get them from... The idea was to plug smbd's knowledge graph, with structured POIs, with curated text, pics and videos. We could easily land you by coordinates to Google Street View instead of Wikipedia. But we don't know yet what people want.
Themes is another big feature. Family or adventure or culture. Known how to do that, just not doing it right now. Thank you again for very consistent and useful feedback. This is going to impact our planning.
Adelaide Daylesford, Victoria Grampians National Park Melbourne
Adelaide is start, Melbourne is finish. Two waypoints in the middle, could be routed, could be skipped, depending on time, budget, comfort, curiosity levels.