Why do my product explanation hotspots disappear when I open native phone AR?

Identify where the explanation actually lives

A furniture merchant may place clickable dimensions, material notes, and assembly explanations around a 3D chair. These labels can appear visually attached to the model while remaining ordinary webpage interface content.

Model-viewer distinguishes browser-based WebXR from native AR viewers. WebXR runs within the browser environment, where DOM interface elements and scripts can remain available. Scene Viewer and Quick Look operate separately and do not receive that DOM content.

The important distinction is between an annotation created by the webpage and information actually contained in the model's geometry or materials. Their visual positions may look similar, but their delivery responsibilities differ.

Before diagnosing a missing label, identify whether it was implemented as a web hotspot or as part of the underlying 3D asset.

Match the information plan to the AR route

If shoppers must read a product dimension while examining native AR, do not assume a webpage hotspot will follow them into the native viewer.

Keep essential product specifications accessible through a separate readable product page or information section. This provides a reference independent of the AR presentation.

Embedding changing information such as prices directly into model textures is not a universal solution. It creates another asset-maintenance responsibility and may leave outdated information inside delivered models.

For WebXR, evaluate whether the intended interface remains available in the actual browser configuration. HTTPS and appropriate iframe permissions, including xr-spatial-tracking where relevant, are environmental requirements rather than evidence that every device supports the experience.

Ask the storefront maintainer to confirm the supported browser configuration for the intended AR route before arranging device acceptance.

Illustrative exercise: furniture labels in two environments

Illustrative exercise — fictional merchant scenarios. No webpage was modified, and no AR device or browser was tested.

Input A is a furniture product page with DOM hotspots describing chair width and seat height. The customer opens native phone AR and no longer sees those labels.

The merchant should recognize the runtime boundary, retain the specifications on the product page, and review whether the native AR journey clearly provides access back to that information.

Input B uses a browser-based WebXR experience intended to display the same explanatory interface. Because the browser environment can retain DOM content, the merchant may evaluate this route, but actual device and configuration support still require verification.

Neither case establishes that a particular phone will display every hotspot.

Review the complete information journey

Prepare separate checks for webpage 3D, browser WebXR, and native AR. Record which environment should display each product explanation.

If the native viewer omits DOM labels, stop treating the issue as a damaged model texture. Instead, decide whether the information belongs in an independently accessible page or another supported presentation.

Verify that customers can still reach essential specifications without relying exclusively on an AR overlay.

The handoff is complete when the merchant has documented which information remains available in each intended environment and which device-specific behavior still needs testing.

This is a content-delivery decision, not a claim that AR devices or storefront integrations have been tested.

Illustrative exercise — Product information across AR environments

These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.

Download review worksheet (CSV)