A few usability suggestions
First,
I believe where Waze has succeeded is in gaining my trust as a user. It is now the only GPS app I really believe when I see an ETA - good job on that. It is also the only reason I use Waze over everything else - because what I care about the most is knowing when I will reach my destination. The social aspects for me are all secondary.
I am using the Android client.
Next, here are some suggestions:
I am more than happy to help test stuff if necessary. Do let me know.
Cheers from New Zealand.
I believe where Waze has succeeded is in gaining my trust as a user. It is now the only GPS app I really believe when I see an ETA - good job on that. It is also the only reason I use Waze over everything else - because what I care about the most is knowing when I will reach my destination. The social aspects for me are all secondary.
I am using the Android client.
Next, here are some suggestions:
- 1) It would be nice if I could re-order my favourites. I live in NZ and when I search for an address, chances are Waze is usually not able to find it. I work around this by browsing around on the map and adding it to my favourites.
2) Please add the option to use Android's built in text-to-speech engine to speak road names out loud. This request comes from my wife as she hardly ever looks at the map, but just listens to road names while driving.
3) Right now, Waze is unable to locate to locate my home address. I have worked around this using the procedure described in (1). However, the Waze application still does not know that this is "home", but rather a favourite that happens to be named home, if you get my meaning.
4) Is it possible to use Google Navigation's strong address search to find an address, but Waze to navigate to it? I find Google Navigation to be extremely unreliable in terms of ETA calculations - even after live traffic has been added.
I am more than happy to help test stuff if necessary. Do let me know.
Cheers from New Zealand.
Re: A few usability suggestions