Design

Controllers Best Practices

Updated: Mar 13, 2026

The following best practices guide the use of controllers as an input method in immersive app design and development. They aim to enhance user experience and ensure optimal performance.

Limitations and mitigations

Every technology comes with its own set of limitations and challenges that must be addressed in order to ensure optimal performance and usability.

Tracking volume

For Meta Quest 1/2/3 controllers, there is a fundamental limitation based on the tracking volume defined by the headset cameras. Primarily, the headset needs to see some portion of the controllers in order to estimate their pose, especially when starting tracking.

Design mitigation

Controllers utilize an inertial measurement unit (IMU), which can estimate position and orientation for a short period when the controller is outside the FOV of the tracking cameras. However, this estimate drifts over time, suffering a rapid degradation in accuracy. Self-tracked controllers do not suffer from this limitation.

Code mitigation

For use cases which are known to stress the position/orientation of the controller with respect to the tracking volume, several physics-based constraint systems are utilized to assist with controller tracking.

Lighting conditions

While controllers are fairly robust to a wide variety of lighting conditions, there can be scenarios where specific conditions will cause degradation in tracking quality. For Quest 1/2/3 controllers, the most impactful conditions are high-intensity lighting or direct sunlight. This is primarily due to the wash-out of the infrared LEDs by the high-intensity light emitted by the sun; however, particularly bright indoor lighting can also wash out the LEDs.

Design mitigation

Our devices adapt to varying light conditions, with continuous improvements through updates and new models. To ensure optimal controller tracking, advise users to avoid high-intensity lighting or direct sunlight, for example through a note at application launch.

Dos and don’ts

Below is a list of recommended practices when using controllers in an immersive experience:

DO Use the Menu button (≡) for menus is strongly recommended, as it provides a more consistent experience across titles.

DO Implement Haptic Feedback: Use haptic feedback to enhance the realism of interactions and provide confirmation of user actions, which helps in creating a more immersive experience. See haptics for more.

DO Maintain Consistent Input Mapping: Align controller functions with common practices across different applications to minimize the learning curve and make the interaction intuitive. See input maps for more.

DON'T Rely Solely on Controllers for All Interactions: While controllers are a primary input method, they should not be the only modality for interaction. Ensure accessibility by incorporating alternative input methods that cater to different user needs and contexts.