Hacker News new | past | comments | ask | show | jobs | submit login

Their motorcycle products have gotten much worse over time (specifically, Zumo 550 to 350).

They've lost physical buttons (it's much, much safer to get back to map view via tactile sensation) and added horrible drag-based panning to the overhead map view. The device can't reliably distinguish between a tap to initiate a drag and a tap to select a point. Selecting a point recenters the map. The two fight one another, usually going in the wrong direction.

It no longer supports an ad-hoc routing workflow. Before, you could select start and end points to your journey, then randomly select waypoints to visit from the map view, and they'd be added in the most sensible order. Now, if you manage to force the map view to point at where you want to go, then it forces you to select the insertion point of the new waypoint in a list, where you can't tell whether you'll be doubling back on yourself. I have to do all my routing in Google Maps now and then add villages to the route using the city finder. Ad-hoc routing by the roadside looking for curvy roads used to be a 60 second activity. Now I need to take off my gloves, pull out my phone, try and find relevant waypoints by name, type them in - it takes 10x as long.

The hardware is woefully underpowered. It feels just as slow as the Zumo 550 first released ten years ago. It can't route distances longer than about 400 miles if it doesn't involve motorways. Recalculation takes up to several minutes. Redrawing the screen in the middle of London after a zoom change can take nearly a minute.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: