UX Encyclopedia

Virtual Reality Design

VR replaces the user's entire sensory environment. The stakes are physical: bad VR design causes real nausea and fatigue. Comfort is requirement zero.

Try it — where spatial UI is comfortable. Move a 0.8 m-wide panel around the user, seen from above. The readout scores each placement against the guidance on this page: the ±30° gaze cone, the 1–3 m optimal band (Alger's zones, Meta's guidance; visionOS pushes UI beyond arm's length), and the panel's angular width — the number that actually decides whether text is legible.
1 m 3 m 5 m ±30° gaze cone

Comfort & simulator sickness (the hard constraints)

Cause: sensory conflict — visual motion without matching vestibular signals (vection). Established mitigations (Meta Horizon OS design guidance; LaViola 2000; Jerald 2015):

  • Never move the camera without user input; never take control of the head. No camera shake, no forced acceleration, no cutscene head-turns.
  • Prefer teleportation or snap-turning over smooth locomotion for general audiences; if smooth locomotion, offer vignetting (tunnel vision during movement), constant velocity (acceleration is the sickness trigger), and always offer comfort options — comfort is individual.
  • Frame rate is non-negotiable: sustained native refresh (72–120 Hz per device); dropped frames and latency (motion-to-photon ideally <20 ms) directly cause discomfort (Abrash/Oculus engineering guidance).
  • Horizon stays level; avoid stairs/elevators/vehicles for sensitive users; give a stable reference frame (cockpit, static HUD elements are risky — prefer world-locked references).
  • Measure with the Simulator Sickness Questionnaire (Kennedy et al. 1993) when testing.

Ergonomics of 3D space

  • Content zones (Alger's VR interface zones; Meta guidance): optimal UI ~1–3 m from the user (closer strains vergence–accommodation conflict; Apple's visionOS guidance similarly pushes UI beyond arm's length for comfort). Keep frequent UI within a comfortable gaze cone (roughly ±30° horizontally from straight ahead); neck rotation for occasional content only; avoid sustained looking up.
  • Text in VR: much larger than 2D habits; high contrast on simple backdrops; test on lowest-resolution target headset.
  • Fatigue: "gorilla arm" — no sustained mid-air arm raising; interactions at waist/chest height, short bursts, support resting poses; sessions should have natural break points.

Input & interaction

  • Support the device's whole menu: controllers (haptics! use them for confirmation and texture), hand tracking, and gaze+pinch (visionOS's primary model: look at target, pinch to act).
  • Hand-tracking maturity (as of 2025–26): standard on Quest-class devices and the only input on Apple Vision Pro. Reliable for coarse gestures — pinch to select, point/raycast, grab — and poor for fast, precise, or occluded poses. No haptics: compensate with strong audio and visual confirmation. Keep the gesture vocabulary small; support controllers wherever they exist; design targets and dwell tolerance for tracking jitter.
  • Direct manipulation beats abstract UI in VR: grab, place, turn — leverage physical intuition (proprioception is a superpower here).
  • Raycast pointing for distant objects; oversized targets (angular size matters, not pixels); strong hover/focus states since pointing is imprecise.
  • Diegetic UI (in-world: a watch, a tablet, a control panel) usually beats floating HUDs for immersion and comfort.

Passthrough & mixed reality (now the default context)

Color passthrough is standard on current headsets (Quest 3 class, Vision Pro), and many sessions start in the user's real room rather than a void. Norms from Meta's MR design guidelines and visionOS HIG:

  • Anchor virtual content to real surfaces (walls, tables, floor) via scene understanding and spatial anchors; correctly scaled and occluded content reads as "there."
  • Don't teleport or relocate the user in MR — their sense of place is the real room; moving content is fine, moving the world is not.
  • Transition between immersion levels (passthrough → full VR) gradually — fades and growing portals, not hard cuts (Meta's "Mixed Reality Motifs" patterns).
  • Design for uncontrolled rooms: small spaces, clutter, other people; never obscure real hazards.
  • Spatial persistence is now an OS-level expectation: visionOS 26 (2025) keeps widgets and windows where the user left them across sessions; Quest spatial anchors do the same for apps that opt in.

Presence & environment

Presence (the feeling of "being there" — Slater's place illusion & plausibility illusion) is VR's core value; it's built from consistent physics, spatial audio (a major and underused channel), responsive environment, and scale accuracy — and broken by clipping, floating UI, frame drops, and unresponsive objects. Sound design and lighting carry enormous presence weight relative to cost.

Accessibility in XR

Immature but no longer optional. Reference points: W3C's XR Accessibility User Requirements (XAUR) and the XR Association's developer guide chapter on accessibility. Emerging norms: subtitles/captions with speaker indication (spatialized or screen-fixed with care); seated and one-handed modes; remappable inputs and controller/hand parity; alternatives to motion- or gesture-gated content; adjustable text size and high-contrast UI; visionOS ships Dwell Control, Pointer Control, and VoiceOver in spatial contexts — support them rather than bypassing system input.

Safety & social

Respect guardian/boundary systems; design seated & standing modes; personal-space bubbles in social VR (harassment mitigation — now standard in Horizon and most social platforms); comfort settings menus as a norm.

Sources

  • Meta Horizon OS developer design guidelines (developers.meta.com/horizon/ design) — comfort, locomotion, hand tracking, and mixed-reality design (formerly "Oculus best practices").
  • Jerald, J. (2015). The VR Book: Human-Centered Design for Virtual Reality. ACM Books / Morgan & Claypool.
  • LaValle, S. (2017). Virtual Reality. Cambridge UP (free online).
  • Kennedy, R. S. et al. (1993). "Simulator Sickness Questionnaire." Int. Journal of Aviation Psychology, 3(3); LaViola, J. (2000). "A discussion of cybersickness." ACM SIGCHI Bulletin, 32(1).
  • Slater, M. (2009). "Place illusion and plausibility…" Phil. Trans. R. Soc. B, 364.
  • Alger, M. (2015). "Visual Design Methods for Virtual Reality" (widely circulated methods paper on VR content zones).
  • Apple — visionOS Human Interface Guidelines (developer.apple.com/design); Apple Newsroom (2025) — visionOS 26 spatial widgets & persistence.
  • W3C — XR Accessibility User Requirements (XAUR), W3C Group Note; XR Association — Developers Guide, accessibility chapter (xra.org).
  • LaViola, Kruijff, McMahan, Bowman & Poupyrev (2017). 3D User Interfaces: Theory and Practice (2nd ed.). Addison-Wesley.
↑↓ to navigate · Enter to open · Esc to close