For each context, only a fraction of the app’s overall interaction set is likely to be relevant. Use context-specific interactionsĪny app experience can be imagined as a series of distinct contexts chained together by specific interactions. The solution? Making a fist stops your hand movements from impacting the app controls. But since humans haven’t yet mastered the art of invisibility, pulling your open hand from the interaction space can send you into a tailspin. Google Earth’s Leap Motion integration uses a variety of hand metrics – including pitch, yaw, and position – to let you soar above the globe. If tracking hand position is a key part of using your app, remember that users will want to completely stop tracking without having to remove their hand from the device’s field of view. Our internal testing has also found that bringing in two hands for an interaction is more explicit than a single one, and therefore harder to accidentally trigger. In All the Cooks, for instance, switching from an open hand to pointing reveals additional menu options. One approach is to use clear switches in hand poses. Design explicit trigger actionsĪctions that require more user intent than others will always be harder to trigger accidentally, and should be used when a false positive could disrupt the entire experience. This gives the user time to return to the original position without accidentally triggering a second swipe. To avoid registering a false positive, you can design your app to ignore subsequent swipes within a brief time window (one or two seconds) after the initial swipe. Let’s start with our earlier swiping example. So, with hand data being tracked constantly, how do you stop hand interactions from colliding with one another? 1. ![]() This is a false positive error, and bad UX. When the user swipes right and naturally pulls the hand back to its original, the left swipe might get triggered accidentally. Let’s say there’s an app with two controls: left swipe and right swipe. ![]() Instead of designing interactions in black and white, we need to start thinking in shades of gray. Motion control offers a lot more nuance and power, but unlike with mouse clicks or screen taps, your hand doesn’t have the ability to disappear at will. For touch-based input technologies, triggering an action is a simple binary question.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |