I had a route mapped out on the website and when I was ready to drive, I plugged in my iPhone into my car and opened the GAIA app in CarPlay. Great, the map shows up, tap on the screen I see the routes button, tap on that., my list of routes are displayed. However, the route I've set up displays this:What does that even mean? What do you mean "(directions aren't available)"? From the app on my phone I try to use get directions with app and what happens: Apple map opens up and routes me immediately back to my starting location. Same with google maps. WTF?!
So, I think: I'll use InRoute, I have used it for a few years now. Export the .gpx or the .kml and lo and behold the GAIA map file has like 8000 points in it. And InRoute displays the entire route as dropped waypoints, which makes it virtually unusable and bogs both the phone and map app.
This leads me to my UI/UX questions:
1. Why is there No path for me to understand how to get directions for that route? For instance: why not provide feedback on carplay, or direct the customer to someplace in the app to help them/me understand how to fix this "error." The ux/ui element is called a Dialog, or a Modal. Even if you provided it on Carplay it could still talk to the app, push a notification to your app.
2. Provide a better export for map files for other software that isn't 8000 points and doesn't overwhelm those apps.
3. Separate from my recent experience why do I have to go into the app and change line size of a route to get it to display on the CarPlay map.
It's super frustrating, GAIA is such a great tool for map planning, but it seems it's inconsistent tor actual active directions. I have to do double the work to actually use my GAIA route; Create route, export, import into InRoute, and edit the route for what feels like an hour.
Please sign in to leave a comment.