I've also developed a Waze habit for the "additional" information it can use. Traffic, construction zones, etc.
I also kinda like that the community can update it. I've fixed a couple of rural road intersections out here near the house, including one that's fenced off that it used to think was open. The online editor is pretty nifty, and their "trust" model lets anyone edit, but only higher level folks to approve changes.
Over time their maps just get better. And it's free.
Installed two lovely Kenwood/Garmin stereos in two of the trucks. Liked it. Has traffic. But doesn't have all the other stuff Waze has. And wasn't clear that unlike some Garmin units with "lifetime maps", these don't. Garmin wants $70/year per vehicle to update the maps.
Guess which two expensive GPS devices in the dash don't get used much anymore and haven't been updated in two years? **** off Garmin. The data is free and the app runs on my phone now. Those dash mounted expensive to update units with less features, are essentially obsolete, unless I forgot my cell phone. I stick the phone in a RAM mount now and plug in a charging cable.
All I use the Garmins for now is fuel mileage. They accurately track miles between full ups, so I just enter price and gallons and done.
I can't turn any of those on where I live. "Avoid dirt roads", nope. "Avoid seasonal roads," maybe if they've updated the county road from unpaved to paved status. Even "avoid toll roads" is sometimes inappropriate if I need the ten minutes back that using the highest priced toll road per mile in the country will get me, from time to time, on certain routes.
The other Garmin feature of "avoid this road" really sucks on the UI to do when you're not ON that road, I've noticed.
Love those Kenwood in dash gadgets for their music abilities and iOS integration. But the Garmij module could drop dead in them, and I wouldn't miss it. Not at the price Garmin wants for map updates.
Only thing Waze needs to play catch up on against anyone else is depicting multiple lane exits. It needs that feature badly.
I found Waze pretty useless, actually (aside from being a bit creepy and sometimes corny). Even once I dismisses the creepiness and the corniness, Waze doesn't download and cache sufficient map data to make a long trip through areas with spotty cell coverage possible, especially when departing from a cell phone dead zone. The routing can then become very bizarre because it bases it on whatever information it happens to have in cache. On one test, it picked a route that would have added more than 135 miles through two states to a 60-mile intrastate trip; and when I ignored its suggestion and took the most direct route, it simply stopped routing.
What I suppose happened was that at the time I entered that destination, the app neither had not was able to download the basemap for the area through which the best route passed; so at that moment in time, it literally didn't even know that that little piece of the world existed. It based its route on what it knew. Apparently Waze limits the cached data to a fifty-mile radius of your starting point and downloads the rest on-the-fly -- assuming that you spend enough time in areas where it has a data connection to complete the downloads. If not, then things get wonky. (It does apparently cache the maps for any place you've been in the past 30 days, however; so if you tend to travel to the same places all the time, probably you won't have any out-of-data issues.)
I doubt that Waze will ever allow for more offline map caching because their entire model is based on data collection, and they don't want to enable users to shut off their data connections and still use the basic navigation app. The amount of data that it collects and send back is staggering; and considering that Waze is owned by Google, I'm sure that data is being monetized somehow beyond the on-screen paid POIs. Without the telemetry, maintaining the app serves no business purpose for them.
In fairness, however, someone has to pay for the service; and frankly, if one want absolute privacy, then one shouldn't use a real-time phone navigation app at all. They should use a freestanding GPS device without telemetry, or a phone app with offline maps stored and live features disabled. Garmin's newer freestanding devices use a one-way traffic data download service from NavTeq that doesn't require a data connection at all, and most phone navigation apps that offer offline maps will function in basic navigation mode with data services disabled. But if one wants real-time traffic, cop locations, and so forth, it's impossible to deliver that data without first collecting it (and, of course, knowing the user's location). You can't have one without the other.
Nonetheless, when the app publisher's restrictions on offline map caching adversely affect the basic design purpose of the app, that's a problem. Many other navigation apps do manage to take a middle course by allowing offline map storage of the whole country, if you care to download and store that much data, to get you through the dead zones; but also live services for when you do have and elect to use a data connection. Waze doesn't offer that option. If you drive through enough dead zones where you haven't been recently enough for the app to have cached that data for you, you're going to have problems.
In addition to the lack of map caching, Waze lane guidance is literally non-existent. Waze also doesn't seem to grasp the concepts of jughandles or traffic circles. But in fairness, very few phone navigation apps do. Sygic and TomTom were the only phone apps I tested that consistently understood the concept of exiting right to make left turns, and knew which turns to take to exit traffic circles and roundabouts (which apparently are two different things, although I have no idea what makes them different).
I suspect that the ability to comprehend jughandles, traffic circles, and roundabouts is basemap-related. Both Sygic and TomTom use TomTom basemaps and are able to negotiate them with no problems. OSM and Google-based apps usually get them wrong. NavTeq appears to understand them, judging by my freestanding Garmin unit; but I didn't test any NavTeq-based mobile apps because Navigon (owned by Garmin) is too expensive and doesn't offer a trial version. It's also possible that the OSM maps do contain that data, but that the apps I tested didn't interpret or implement it well.
All in all, I considered Waze the absolute
worst of the navigation apps I tried. Probably in the cities it's better; but out here, I found it worse than useless, especially when departing from locations that didn't have data service. The only two phone navigation apps I've tested so far that I actually like as well as or better than a freestanding unit are Sygic and TomTom's own "Go" app. The rest have varied from "horrible" to "meh." I'm still testing others.
Rich