No doubt, every one of you is familiar with that unpleasant feeling when you set a destination in Waze—a place or address you’ve never been to—and Waze leads you somewhere in the middle of the street and happily announces that “That’s it, you’ve arrived.” You look around, but the destination is nowhere to be found. You start asking the locals. Eventually, while muttering curses, you drive through unmarked alleys and various internal roads, and when you finally reach your destination, you pray you won’t forget how to get back to where Waze actually knows how to guide you.
Why am I saying this? Because I sometimes get comments about over-detailing the map. Even though the app has improved significantly since the first smartphones with crude GPS components hit the market, and technically it is certainly capable of handling maps of any complexity level, provided they are built according to technical limitations—thresholds that must not be crossed so the app doesn’t confuse adjacent roads. Of course, I never violate these technical limitations.
From my perspective, a navigation map should be built with the driver visiting the location for the first time in mind. The navigation device should bring them to the point where the driver definitely won’t get lost in an unfamiliar place. Also, we shouldn’t forget delivery services, medical aid, and security forces, including the fire department. Especially in these very unsettled times.
So, I try to balance the desire to help everyone behind the wheel with the need to avoid over-detailing, so as not to overload someone’s iPhone 3G running FreeMap Israel (the mother of the current WAZE). This leaves drivers a great opportunity in certain places to still interact with the people around them ![]()
And what about you? What was your reason for becoming an editor? ![]()