New answers tagged zooming
In the time crunch scenario, with User testing going against your darling, i would advice you to fallback to more reliable feedback approach, and rethink the feedforward approach for future release. I like your concept of feedforward, and makes sense. But without seeing the actual UI I am not sure how we can communicate to the user. You need to work there.
As a general rule i definitly advice you to "kill your darling" when it's not working as intended in user tests. Remember, you're not designing this UI for yourself, you're designing it for your users However, it would help if you show a screenshot of how the interface looks, maybe there are other problems causing the users to not understand the buttons ...
It's possible that using touch gesture(s) in this instance to interact with the camera zoom may not be the best choice. Yes, faking a zoom on the client is one potential option, however you're still going to need to incorporate the real image at some point, possibly after some additional movement (i.e. left and right) has occurred - this disconnect could ...
As for the gesture to use for zooming, you could investigate a "double-tap + scroll" as Google Maps does. The added visibility of the screen may aid in the user's ability to deal with the latency. To help avoid latency you could try a client-side digital zoom, and let the camera "catch-up". In this case when zooming in the image would use a digital zoom ...
Top 50 recent answers are included