Android AR on Product Pages: Keep a Useful Fallback

If the room preview does not open on Android, keep the product page useful. Leave shoppers a working browser-based 3D view where available, plus photos, dimensions and the purchase or enquiry action. Then test which part of the Android route failed before changing the model or the page.

For ecommerce teams piloting SwiftXR on a catalogue, test the published SwiftXR project by itself and then test the same experience from the product page. The SwiftXR HTML integration guide covers publishing and embedding. A standalone check helps separate the experience from its placement on the store. A second check tells you what the shopper sees when they start from the actual product page.

Decide what the shopper should still be able to do

Take a desk lamp as an example. Someone considering it may want to inspect the base, check the footprint and see roughly how the lamp looks on a desk. The browser viewer can help with the first task, and the published dimensions answer the second. Room preview helps with the third on a device where placement works. Keep those jobs separate in the page design.

Make the fallback answer the first two questions. Put the product dimensions and the main action in the product page itself. Leave photos available even if the viewer never loads. If your layout replaces the gallery with a blank panel when AR is unavailable, the buyer has lost more than room preview.

Work out where the Android route stops

Open the live product page on an Android device you plan to support. Record the device model, Android version, browser or app used to open the page, and the exact product URL. Test the standalone link on the same device, then repeat from the store. Note what happens after the AR tap and what happens when you return.

The browser viewer never loads

Check whether the standalone project loads on the same phone. If it loads there but the embed fails, give the web team the exact page and embed context. Keep the product gallery visible while you investigate. If neither route loads, test a known working project separately before concluding that the catalogue model needs replacing.

The product opens in 3D but never reaches placement

Find out which AR route the experience uses. For Google Scene Viewer, Google's documentation distinguishes launch modes that favour a 3D view, prefer AR with a 3D fallback, or request AR only with a fallback URL. A 3D screen can be an intentional outcome of that launch mode. Google also publishes a list of ARCore-supported devices. If your route uses browser WebXR instead, check Google's WebXR requirements separately. These are platform checks. Ask your provider which route your published experience uses before applying instructions for either one.

Placement opens, but the shopper cannot finish the purchase

Close the room preview and return to the store. Check that the same product and variant are still clear, the buyer can find the dimensions, and the purchase or enquiry action works. Repeat the return journey after a failed launch. A successful placement is only one part of the release check.

Set separate acceptance criteria for 3D and room preview

Use one product and a small test set before scaling the rollout. Include a supported Android device, an Android device or context where room preview is unavailable, and the desktop product page. If a campaign opens the store from an in-app browser, include that route as a separate case. Keep one record per entry route so the team can reproduce failures.

• Browser view passes when the approved product is recognisable and the intended details can be inspected with touch.
• Room preview passes on the supported route when placement opens and the correct product appears. Check the intended scale against the approved dimensions separately.
• Fallback passes when a shopper who cannot open room preview can still find the right photos, dimensions and next action.
• Return passes when the shopper can leave the preview and continue from the right product page.

An expected fallback can pass even if that device cannot launch room preview. Record unexpected failures separately and route them to the person responsible for the product page, experience or device test. This gives the team a release decision tied to shopper tasks.

Start with the product where placement matters

Pick one SKU whose size or position buyers routinely ask about. Bring its approved model, published dimensions and actual product-page layout to a SwiftXR demo. Ask to run both the standalone and embedded routes on a test phone. Use the SwiftXR 3D model viewer to assess what the shopper can still inspect when placement is unavailable.