Tag Archives: Waze

Waze 3.7.2 dimming bug

Waze 3.6 was very stable.

Waze 3.7 crashed frustratingly often. They redesigned the alerts, with a popup on the top, a close button on the right that appears after a few seconds, and a dimmed display that highlights the location of the alert. All good, except that Waze would almost always crash whenever an alert popped up. And immediately crash on restart until the alert no longer displayed, probably when it was out of range.

Waze 3.7.2 no longer crashes with alerts, but they introduced a new bug. The display now dims with the highlight on or near my current location even if there is no alert. Only the main menu and report buttons work. I cannot scroll or zoom. Are they testing before release?

IMG_3015 IMG_3041 IMG_3040 IMG_3026 IMG_3016

Be Sociable, Share!

    Google’s acquisition of Waze

    I am worried about what Google will do to Waze. Waze involves users directly. Google does not like direct user input. Google likes crunching gobs of data on user behavior. Google trusts aggregate data more than people. While that might allow Google to correctly guess what I meant to search for (because 99% of the time, other people made the same typo), it may actually degrade route calculation. Google calculates the best route from A to B based on speed, distance and traffic. Plus Google knows that 99% of people take that route even if it is not the best route. But, 1% of people know a faster/easier route (and that benefits the 1%). Will Google allow that 1% to override the 99%? Waze has learned my shortcuts (that are consistently faster than Google’s or Waze’s calculated routes) and now presents them as the default route.

    Related, Waze allows normal people to instantly alert others of an accident, construction, etc. Google relies on public sources like Caltrans, CHP etc, which are once removed from the source data. A minor accident which causes a major local backup but is never reported to CHP would not show up in Google Navigation, but could in Waze. Google may show the reduced speed but not the cause.  How will Google integrate Waze’s crowd-sourced data?

    Update 20130614: @TechCrunch With Waze, Google Gets Access To Social Mapping Data — And Possible Patent Legal Heat From Nokia

    Be Sociable, Share!

      Google Navigation vs. Waze

      Funny, I started writing this the day before the possible purchase made the news.

      I have been using Waze for 3 years. Whenever I am on the road, I run Google Navigation on my Droid 4 and Waze on my iPhone 4S. Google used to give incredibly accurate (to-the-minute) ETAs but something changed in the last few months, their ETAs have been increasingly wrong (optimistic). Google clearly has more speed data than Waze (unless you opt-out, every Android phone constantly uploads position and speed information) and yet, Google seems to have forgotten how to factor in delays caused by traffic jams enroute. Waze never did this well either so now they’re about the same ETA-wise.

      Both are frighteningly good at predicting my next destination. Normally, both ask if I am going home from daycare. But Google has learned that Wednesday is usually pizza night and asks if I am going to Costco instead. Google presents a sorted list so I can easily select the top entry. Waze asks if I am going to X and automatically routes to X if I do not press anything for 10 seconds.

      Google pluses:

      • One button toggle between display of entire route and local (navigation) view.
      • One button display of alternate routes with distance and drive time for each.
      • Usually more accurate display of traffic speed (compared to Waze).
      • Usually better route calculation (compared to Waze).

      Google minuses:

      • No user-reporting of incidents. Far too often, Google will think the freeway is clear when it is actually a parking lot due to a stalled vehicle. But there is no way for me to warn other people.
      • Refuses to consider surface streets as an alternate route.
      • Refuses to use carpool/express/HOV/HOT lanes. In fact, Google does not seem to know how to handle them at all because while I am in the carpool lane, Google constantly suggests ludicrous routes to exit it.

      Waze pluses:

      • Cleaner local (navigation) view with useful info: speedometer, ETA, miles to go, remaining drive time.
      • Rapidly reported, accurate, crowd-sourced incident and traffic information (compared to Google’s reliance on Caltrans / CHP). Crowd-sourcing is obviously better if there are many active Waze users in your area.  Also, I often send alerts with photos.
      • Prettier interface.

      Waze minuses:

      • Occasionally faulty route calculation. Sometimes Waze knows an alternate route is slower (ETA is later) but still displays that route.  Sometimes the detour is obviously slower to an experienced driver because it involves multiple left turns at uncontrolled intersections.
      • Needs single-button entire route display like Google.

      I took screenshots of both Google and Waze on a typical drive to daycare.  At startup, Waze guesses I am driving to daycare and presents some useful information – ETA, distance and traffic on route summary:

      IMG_2840

      Once on our way, Google’s presentation of street and freeway traffic conditions showed a large segment of surface street without speed data (grey) and moderate traffic on the freeway:

      Screenshot_2013-06-11-08-05-29

      Waze’s presentation shows Wazer-entered traffic alerts and two absolute speeds, which are different from (and more accurate than) Google’s:

      IMG_2843

      Waze’s distinguishing feature are Wazer alerts which are usually very accurate:

      IMG_2846

      Both Google and Waze occasionally suggest a “better” route that is actually worse.  Here Waze suggests a “better” route that has an ETA of 08:47 while the ETA for the current route is 08:46.

      IMG_2847

      Google’s entire route view presents much more useful information than Waze.  Here, Google thinks traffic is slow ahead while Waze shows no data. I have to click on the Wazer alerts to see their content.  They may warn that the freeway is slow but I should not have to click on them while driving at 57mph to find out.

      Screenshot_2013-06-11-08-21-47

      IMG_2849

      But later, Google mistakenly thinks the freeway is completely clear while Waze correctly says it is not:

      Screenshot_2013-06-11-08-35-05

      IMG_2857

      Photo showing actual traffic:IMG_2858c

      Google’s alternate route display is much better:

      Screenshot_2013-06-11-18-05-57

      than Waze’s default:

      IMG_2866

      Clicking on Map brings up a much more useful display, though I still have to pinch-zoom to enlarge:

      IMG_2867

      And another example of Google vs. Waze alternate route calculation.  Waze correctly suggests the carpool lane which is the faster route.

      Screenshot_2013-06-12-08-27-54

      IMG_2877

      And an example of Waze’s incorrect “detour” routing. It wants me to make a left turn (controlled) at a very busy intersection, right turn onto a side street with stop signs, then left turn (again controlled) back onto the same street. Local drivers are smarter than the algorithm, we know this would be far slower.

      IMG_2874

      I am hoping that Google assimilates some of Waze’s better features: user reporting, surface street routing and carpool lane awareness.

      Be Sociable, Share!