San Diego, CA metro is now between 300-500 Wazers at the peak of rush hour. I believe the single largest number I have seen myself is 447. This is up from a couple of hundred after Waze 3 for iPhone released and up from < 100 prior to Waze 3 for iPhone. I have definitely noticed that use is higher when the weather is bad (bad weather = rain in San Diego) or when traffic is unusually heavy. I agree with comments that Krankyd made in Palo Alto that Waze has a challenge in getting users to run Waze EVERY time they drive vs. just turning it on sporadically.
Hoping to see 1000 Wazers 'near you now' in the near future. If a local TV station would pick up 'Waze TV' for traffic reports I feel we could see explosive growth in San Diego.
As I have mentioned in other threads, due to very proactive editing work by a few very active editors in San Diego the maps are very mature and accurate here. We have been proactively editing street by street, neighborhood by neighborhood. (although not all that organized unfortunately) The map maturity in San Diego is MUCH
better than nearby metro areas such as Orange County, Los Angeles, CA, and San Francisco/Silicon Valley.
I really feel that having fully edited maps is of very high importance to an increase the number of Wazers 'near you now'. Of course it also helps if there is traffic that needs to be avoided
Straying slightly off-topic - Now if Waze could get us better solutions to the following problems, Waze could really grow:
* Routing issues due to algorithms that need tweaking.
* False traffic reports in residential neighborhoods due to jam algorithm that needs better validation of jams.
* goodie/cookie munching setting that needs to be removed a month+ ago, causing bad routing.
* Pave mode that is overused in an area with mature maps.
* The overmapping of parking lots.
* No valid solution for basic Parking Lot mapping (Parking Lot roads are causing more problems then they solve due to the issue with not respecting turn restrictions and least segment path out of the Parking Lot vs. correct routing). Parking lots stubs are not viable either.
* Other back-end or client issues that cause end-users to have a bad experience with Waze.
* Map updates too slow to propagate to the app as the tile building is being re-vamped.
* No exposure to whom edited a junction last. Would be very useful to help out editors who are making errors.
* Better up front communication with Wazers that they can edit the map, how to submit an Update Request with details of the problem, better way to deal with routing when off-network (more of an issue now with CDMA iPhones and no cellular data when talking on the phone).