You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Be more dynamic, communicating maneuver urgency by camera distance/zoom level
Be timed with voice announcements: what's communicated on screen should match audio cues
Provide ample context for maneuvers
As a rough first pass, we should implement basic stepped camera movements achieving the following:
Triggered by/synchronized with voice announcements
On the completion announcement of a maneuver: zoom out to provide context for long steps with long periods of inactivity
At the first approach maneuver announcement (In 2 miles...): zoom to show the upcoming maneuver on the map, whether by a fixed zoom level based on distance, or a zoom to fit function.
At the final turn maneuver announcement: zoom in closely to our current default zoom level
Once this basic set of triggers/logic is in place, we can experiment with more sophisticated zoom logic, camera tilt, anchor points, etc.
cc @mapbox/navigation-android
The text was updated successfully, but these errors were encountered:
Don't want to hijack this at all. Thought about the camera and its zoom levels the other day. But having basic camera movements in relation to maneuvers sound great. My two thoughts were:
Allow the user to set the zoom level (don't override it when pressing re-center)
Zoom levels depending on speed
Both might be fixed with camera movement on voice announcement, but as of now the first one feels quite important since it's really annoying from a UX perspective that it takes over the zoom at re-center.
Android version of mapbox/mapbox-navigation-ios#773
The camera should:
As a rough first pass, we should implement basic stepped camera movements achieving the following:
In 2 miles...
): zoom to show the upcoming maneuver on the map, whether by a fixed zoom level based on distance, or a zoom to fit function.Once this basic set of triggers/logic is in place, we can experiment with more sophisticated zoom logic, camera tilt, anchor points, etc.
cc @mapbox/navigation-android
The text was updated successfully, but these errors were encountered: