was not uploaded on 2.2, but still under consideration for the next version.
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.
This is less an issue about map contributions and more about UI experience.
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.
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.
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.
Oh, this one's basically in here already, but the other has more votes. Is there any way to merge suggestions?
You'd also want to hear when the app's recommended navigation diverges from your standard commute.
201 votesMisha Syeed supported this idea ·