The next step after evaluation is to narrow down the final two sets that were narrowed from from the bigger collection of gestures is to A/B test. For the A/B test, I figured that instead of having two user groups and have one group interact with prototypes using both the A and the B variant that we evaluated and finalised from the mountain of gestures that we collected from user test no.1 & no.2.
Below are gifs that demonstrate the flow of the two sets of gesture patterns. The browse isn’t illustrated properly but the same gestures are involved, except it involves a dragging motion to “scroll” before the fist or pinch is let go (start & finish states).
A: Point to Pinch to Point-pinch-drag-point
B: Palm to Grab to Palm-grab-drag-palm
About A/B Testing
What is it? A/B testing helps observe how one version of something performs against another. It is testing multiple versions of a design to determine which version generates the most conversions. What’s the user’s preference? Which one performs better?
Why? A/B testing eliminates guesswork and avoids assumptions, it validates or invalidates hypotheses, and helps us understand the features and elements that best improve user experience.
How? 1. Research 2. Formulate Hypothesis 3. Create variation 4. Run!
Formulate a Hypothesis by predicting what do you expect the result to be.
Observe which version is performed more intuitively Ask for feedback like why the users prefer A over B or vice versa.
Give the A/B test enough time to produce useful data.
Questions (to myself): What is my hypothesis? What do I expect the results to be? How large is the sample size? Which metrics am I measuring? Should I tweak the prototype before testing?
Questions (to users):
After each set
How did you feel about these gestures?
Which specific gesture felt most comfortable to perform?
After both sets
How did the gesture sets feel compared to one another?
Which one felt more comfortable to perform?
Which one do you prefer? Why?
Journal with me! 