Engine & runtime
WebXR showroom
The same Threlte scene, on a headset — and an honest support check.
What this is
A product showroom wrapped in @threlte/xr, with controller and hand tracking mounted and live WebXR capability detection.
The scene is not a separate VR build; it is the same Threlte scene the rest of this site uses, wrapped in <XR>. Support is detected and reported honestly, because on most devices that visit this page the answer is 'no headset', and a demo that pretends otherwise teaches nothing. The panel covers what genuinely changes in a session: the frame budget doubles, DOM overlays stop existing, locomotion becomes a design problem, and HTTPS becomes mandatory.
Things worth trying
- Read the live VR and AR support verdicts for your device
- Press the VR button — on a headset it starts a session, elsewhere it explains why not
- Shrink the room radius to a realistic 2 × 2 m guardian area
- Note that every label is geometry, not HTML — DOM overlays do not exist in a session
Bring us the product you were told could not be configured.
Tell us the option count, the CAD you already have and the frame budget you need to hit. An engineer reads it and replies with a straight answer — including when the answer is that good photography would serve you better.
We reply to every enquiry within one business day, in your timezone — with a frame budget, not a brochure.