Misha Syeed
My feedback
6 results found
-
3,305 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
Misha Syeed
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment Misha Syeed
commented
This is less an issue about map contributions and more about UI experience.
An error occurred while saving the comment Misha Syeed
commented
The annoying thing about the "Sleep Mode" is that it's not really a sleep or a pause, but a deactivate -- meaning they didn't really add a feature at all, just took away the former way to quit the app.
The response when you "sleep" and then "reactivate" the app is identical to if you force quit the app and start from scratch -- slow relaunch, reacquire network, determine if navigation had been running, recalculate route, ask for confirmation. In fact, the old quit was better, because now to "quit" you have to sleep AND switch apps, one extra click each time.
The requested feature was one big, easy to hit button that just halts map data in/out and audio feedback, but better remembers your place intended for short detours -- pulling over to look up something/at something, drive-throughs, etc. Saving battery in such cases is rarely an issue.
-
18 votesMisha Syeed
shared this idea
·
-
217 votes
Thanks for your feedback. At this time, this doesn't fit on our roadmap, but we'll keep it in mind for future product planning.
An error occurred while saving the comment Misha Syeed
commented
I forget where I heard, but apparently they do not know where the lights are unless someone has reported it as a red-light camera.
Misha Syeed
supported this idea
·
An error occurred while saving the comment Misha Syeed
commented
In major cities (Los Angeles in my case), turning left onto or crossing a major street from a smaller one that is unprotected by a traffic light creates a major slow-down in a Wazer's route and can be dangerous. However, at times of zero-traffic, or in less populous cities, I have seen the benefit first hand.
Perhaps strongly disfavor navigation of this kind when the apparent vehicle load of the target road/crossed road is sufficiently greater than that of the source road.
Or perhaps carefully analyze how long that particular left turn/cross takes Wazers on average to complete in those traffic conditions and stop recommending the slower ones. (After all, some minor streets ARE protected by a light, and those are still useful.)
-
158 votes
An error occurred while saving the comment Misha Syeed
commented
The problem isn't when there's heavy traffic -- in those cases, usually the complicated routes actually serve to get you around traffic quite handily. The problem is the complicated route is still suggested even when there is NO traffic.
An error occurred while saving the comment Misha Syeed
commented
Based on my observation, Waze tends to throw up extremely complicated navigation at times. When following its advice in times of heavy traffic, the route is very fast and useful. However, even at times when roads are abandoned and taking major thoroughfares would be simpler and yield similar time/distance results, the convoluted path is still the one suggested.
I would hope the algorithm would weight every turn as a negative so that a turn would only be added in those cases that it provides an obvious time/distance gain at the time of navigation.
Misha Syeed
supported this idea
·
-
238 votesMisha Syeed
supported this idea
·
-
306 votesMisha Syeed
supported this idea
·
An error occurred while saving the comment Misha Syeed
commented
There are already many options which affect a Wazer's routing, and many many more suggested on these forums. But sometimes a user will deactivate features without realizing their worth. For example, I never want to take a toll road, so I have those disabled -- but if I was stuck in traffic, and a toll road could save me some ridiculous amount of time, I might consider it, despite my usual preference.
So I would propose that any preferences which affect navigation can sort of "self-activate." Perhaps the user could set a time or distance delta threshold before the option flips on. Or perhaps when Waze determines that it really really is in the driver's best interest, it can suggest using that feature (rather than just rerouting).
The issue is that the "pause"/"sleep" currently available is an inane implementation from a user perspective. It is effectively just turning off the app (and replaces that former functionality). However, the former power button obviously closed the app and did so in fewer clicks. The newer sleep has no advantage over the previous version -- slower to implement, no faster to relaunch. If you don't click away from the app, it's too easy to accidentally "wake" the app, at least on iOS: any interaction with pop-over or pull-over interfaces registers as returning to the app and wakes it. And all the routes must be recalculated and reconfirmed by the user. If you were in the middle of a multi-stop route, only one destination is remembered. It is not an effective pause. It is quite frankly advantageous to the user, currently, to force quit the app when they want to pause (or stop) -- faster and less likely to respawn.