AR

AR is one button. What it does depends on the device, and the widget decides.

	What runs	Needs
iPhone, iPad	Quick Look	a USDZ, which the pipeline builds
Android, Chrome	WebXR, in the tab	allow="xr-spatial-tracking"
Android, no WebXR	Scene Viewer	a GLB
Desktop	a QR the phone can open	the page reachable from that phone

WebXR in the tab is the one worth knowing about: on Android the room appears inside your page rather than in the system model viewer, so the price, the size and the “leave a request” button are still on screen while somebody is looking at a cabinet standing on their floor.

In an iframe

allow="xr-spatial-tracking; camera"

Without it the button is drawn and the session is refused — a failure that happens in the visitor’s hands rather than in your console. The widget checks the permission before drawing the button and says why instead, but it can only check what the browser tells it.

In an in-app browser

Instagram, Facebook and TikTok open links in their own browser, which cannot do AR. The widget detects it and says so before the tap, with a “open in Safari/Chrome” instruction — rather than after, when a person has already pointed their camera at the floor.