Official beta · hardware evidence

A device name is not a support claim.

The launch gate combines the accepted candidate, a named device/browser evidence cell, and a fresh runtime capability check. Missing evidence produces an unavailable or fallback state—not an optimistic guess.

Current evidence binding

Channel: maintenance
Candidate: Not published
Hardware matrix: No accepted hardware version
Rule: Only a passing current-candidate cell may say supported

Quest-class browsers

Standalone XR

Immersive VR, passthrough, controllers, and hands are independent checks.

Status: checked at launch against the current accepted matrix.

Vision-class browsers

Spatial browser

Immersive or spatial presentation and gaze/hand input require exact candidate evidence.

Status: checked at launch against the current accepted matrix.

Keyboard, mouse, and gamepad browsers

Desktop

A usable non-immersive presentation is verified separately by browser and renderer.

Status: checked at launch against the current accepted matrix.

Touch browsers

Mobile

Touch usability and rendering are verified separately; a phone name is not compatibility proof.

Status: checked at launch against the current accepted matrix.

Read known limitations Inspect capabilities Back to official beta