Over the course of 500-1000 ms the highlight would increase in intensity. This means at first you would barely notice the feedback when looking at a target. So, when providing hover feedback, we recommend using a smoothly blended-in highlight (and blended-out when looking away). Quick sudden highlight changes (on/off) may result in flickery feedback when looking around. Remember, your eyes are enormously fast, quickly darting across points in your field-of-view. What seems great visual feedback for head gaze can result in terrible, overwhelming experiences using eye gaze. Strive for subtle blended hover feedback: Instead of relying on a cursor to inform the user whether eye tracking is working and has correctly detected the currently looked at target, use subtle visual highlights. While it's nearly impossible to interact without a cursor when using head gaze, the cursor becomes quickly distracting and annoying when using eye gaze. Design guidelines for eye-gaze and commit
Download and enjoy the full experience here. This video was taken from the "Designing Holograms" HoloLens 2 app. When you've finished, continue on for a more detailed dive into specific topics. If you'd like to see Head and Eye Tracking design concepts in action, check out our Designing Holograms - Head Tracking and Eye Tracking video demo below. Head and eye tracking design concepts demo In this section, we focus on the specific design considerations for eye-gaze and commit.įirst, our eyes move incredibly fast and are great at quickly targeting across the view.Įye-gaze is ideal for quick gaze-and-commit actions especially when combined with fast commits such as an air tap or button press. In the Eye Gaze Design Guidelines, we summarize general advantages and challenges when using eye tracking as an input in your holographic app. However, eye gaze behaves differently to head gaze in certain ways and comes with many unique challenges.