On this page
- How it works
- Launch methods from mobile web
- 1. Direct intent URL (low-level)
- 2. web component (recommended for ecommerce)
- WebXR vs Scene Viewer trade-off for ecommerce
- Browser and device compatibility (as-of 2026-09-27)
- GLB/glTF format requirements
- Dual-format pipeline: GLB + USDZ
- Ecommerce conversion benchmarks (as-of 2026)
- Shopify implementation
- 2025–2026 updates
- Practitioner gotchas
- Key terms
Android Scene Viewer
Android Scene Viewer
Google's native, system-level AR viewer on Android — the Android counterpart to Apple's AR Quick Look. Renders GLB/glTF 3D models in augmented reality or 3D-only mode, launched from a mobile browser or native app via a deep-link intent URL. Part of the dual-format ecommerce AR pipeline alongside AR Quick Look on iOS.
How it works
Scene Viewer is built into Google Play Services for AR and is available on every ARCore-supported Android device running Android 7.0 (API Level 24) or higher. (developers.google.com/ar/develop/scene-viewer, fetched 2026-09-27)
It runs as a separate fullscreen process outside the originating browser tab. When the user taps the AR button, they leave the webpage entirely for the duration of the AR session; the browser DOM, cart state, and annotations are not accessible from within Scene Viewer. (developers.google.com/ar/develop/webxr/model-viewer, fetched 2026-09-27)
Launch methods from mobile web
1. Direct intent URL (low-level)
A raw anchor tag with the Android intent URL scheme, works in Chrome on Android: (developers.google.com/ar/develop/scene-viewer, fetched 2026-09-27)
<a href="intent://arvr.google.com/scene-viewer/1.0?file=https%3A%2F%2Fexample.com%2Fmodel.glb
#Intent;
scheme=https;
package=com.google.android.googlequicksearchbox;
action=android.intent.action.VIEW;
S.browser_fallback_url=https%3A%2F%2Fexample.com%2Ffallback;
end;">
View in AR
</a>
Required parameters:
file— URL-escaped HTTPS URL to a.glbor.gltffileS.browser_fallback_url— destination if Scene Viewer or the Google app is not available
Optional parameters: (developers.google.com/ar/develop/scene-viewer, fetched 2026-09-27)
mode—3d_preferred(default; starts 3D, user can switch to AR),ar_preferred(starts AR, falls back to 3D),ar_only,3d_onlyresizable— enable/disable pinch-to-scale in AR (enabled by default)sound— URL to a looping.wav/.mp3audio fileinitialScale— sets initial model scale in ARlink— title/link metadata for the model
2. <model-viewer> web component (recommended for ecommerce)
The <model-viewer> component (v4.3.1, Google, Apache 2.0) abstracts device detection and format selection. Adding the ar attribute renders an AR button; on ARCore-capable Android devices it triggers Scene Viewer (or WebXR) automatically: (modelviewer.dev, fetched 2026-09-27)
<model-viewer
src="product.glb"
ios-src="product.usdz"
ar
ar-modes="webxr scene-viewer quick-look"
camera-controls
auto-rotate>
</model-viewer>
The ar-modes attribute controls AR mode priority order. The default order is webxr scene-viewer quick-look, meaning WebXR (in-browser) is attempted first on Android and Scene Viewer is the fallback. (developers.google.com/ar/develop/webxr/model-viewer, fetched 2026-09-27)
WebXR vs Scene Viewer as default: The model-viewer docs describe WebXR as the preferred default AR mode on Android for its continuity advantages (no model re-download, DOM stays accessible, supports annotations). Older practitioner guides still position Scene Viewer as the primary Android AR path. The architectural shift to WebXR-first reflects maturing browser support as of 2025–2026. (developers.google.com/ar/develop/webxr/model-viewer vs practitioner sources, 2026-09-27)
WebXR vs Scene Viewer trade-off for ecommerce
| WebXR (in-browser) | Scene Viewer (native app) | |
|---|---|---|
| User stays in browser | ✅ Yes — DOM accessible | ❌ No — separate process |
| Cart / annotations | ✅ Available during AR | ❌ Not accessible |
| Device coverage | Chrome 79+ on Android 8+ | Broader: Android 7.0+ with Google app |
| Model re-download | ❌ No (reuses 3D viewer asset) | ✅ Separate download |
| Chrome dependency | Chrome 79+ required | Google app required |
| Samsung Internet | Partial / version-dependent | Unreliable with intent URL |
(developers.google.com/ar/develop/webxr/model-viewer; VNTANA Web AR/XR Guide 2026; synthesized from web sources 2026-09-27)
Implication for ecommerce: WebXR preferred for purchase-funnel continuity (user never leaves the page, annotations and product details remain visible). Scene Viewer has broader legacy-device reach and is the reliable fallback for Chrome users on Android 7.0–7.x or devices without WebXR hit-test support.
Browser and device compatibility (as-of 2026-09-27)
| Browser | Scene Viewer intent URL | WebXR AR |
|---|---|---|
| Chrome 79+ on Android 8.0+ | ✅ Primary support | ✅ Yes |
| Chrome on Android 7.0–7.x | ✅ Scene Viewer via Google app | Partial |
| Samsung Internet 13+ | ⚠️ Unreliable with intent URL; use model-viewer | Partial (version-dependent) |
| Firefox on Android | ❌ No | ❌ No |
| Safari on iOS | ❌ N/A — uses AR Quick Look instead | Limited |
| Desktop Chrome | ❌ No (no ARCore) | ❌ No AR |
(VNTANA Web AR/XR Guide 2026; Browser compatibility synthesis from web sources 2026-09-27)
Samsung Internet AR support: VNTANA's official compatibility matrix lists only Chrome for Android AR/Scene Viewer, implying Samsung Internet is not supported. Samsung's own developer documentation and practitioner sources indicate Samsung Internet 13+ has WebXR support for Galaxy devices, with version 24.0.3.2 beta (2025) restoring WebXR immersive-ar sessions after a regression period. (VNTANA Web AR/XR Support Guide 2026 vs Samsung Developer Blog / browser compatibility research, 2026-09-27)
Recommendation from practitioners: use <model-viewer> rather than raw intent URLs for Samsung Internet and edge-case browsers — the web component handles the intent generation and provides a 3D-only fallback gracefully. (web synthesis, 2026-09-27)
GLB/glTF format requirements
Scene Viewer accepts only GLB (binary glTF 2.0) or glTF 2.0 with separate files. GLB (single-file binary) is strongly preferred. (developers.google.com/ar/develop/scene-viewer, fetched 2026-09-27)
For ecommerce production GLBs: (Frame Sixty, Aug 2026; synthesized from web sources 2026-09-27)
- File size target: under 5 MB for optimal mobile UX; Google's documented ceiling is approximately 15 MB
- Polygon budget: 20,000–300,000 triangles depending on product complexity
- Textures: 2048×2048 px recommended; PBR material maps (albedo, metallic, roughness, normal)
- Compression: Draco mesh compression (~5:1 geometry reduction) + KTX2/Basis Universal texture encoding
- URL: must be publicly accessible over HTTPS — no authentication or redirects
GLB file size limit: Google's official documentation cites approximately 15 MB as the practical ceiling. Practitioner sources Frame Sixty (Aug 2026) and 360 Render (2026) recommend under 5 MB as a mobile UX target, stating files above 15–20 MB "create real usability problems." The 5 MB figure is a UX recommendation; the 15 MB figure is closer to the technical limit. (developers.google.com/ar/develop/scene-viewer vs Frame Sixty Aug 2026)
Dual-format pipeline: GLB + USDZ
The ecommerce AR pipeline requires both formats — GLB for Android Scene Viewer / model-viewer, and USDZ for iOS AR Quick Look. (Frame Sixty, Aug 2026)
Shopify's blog (Aug 2026) states that uploading both GLB and USDZ files to a product page enables "automatic optimization" with device-appropriate delivery. Practitioners (Frame Sixty, Aug 2026) warn that materials can render differently between GLB and USDZ formats — "a metallic finish that looks right on Android can look flat on iOS" — and that Shopify's automatic pipeline does not guarantee visual parity. Human QA on physical iOS and Android devices is recommended. (Frame Sixty Aug 2026 vs Shopify Blog Aug 2026)
Ecommerce conversion benchmarks (as-of 2026)
All ecommerce AR benchmarks treat the combined "3D/AR" experience — no head-to-head data exists isolating Android Scene Viewer vs iOS AR Quick Look specifically. (web synthesis, 2026-09-27)
- Shopify merchant data: products with 3D/AR convert 94% higher than flat images — widely cited since 2022, methodology (product category, time window, AB test structure) not disclosed; practitioners describe this as directional rather than verifiable (Frame Sixty Aug 2026)
- IKEA Place: 189% conversion lift for AR users (most-cited AR ecommerce case study; Apple/IKEA data, widely cited)
- Rebecca Minkoff: 44% higher add-to-cart rate, 65% increase in order likelihood (Neural4D 2026 Shopify guide)
- Return rate reduction: up to 40% (Shopify and Deloitte data, as-of 2026)
- AR users: 21% higher revenue per visit, 13% higher AOV (Zolak 2026)
- Vertebrae: shoppers spend 75 seconds with 3D viewer vs 49 seconds without
- AR ecommerce market: $6.3 billion (2024), projected $74 billion by 2035 (Markets and Markets, via Frame Sixty Aug 2026) / $9.1 billion (2025), projected $67.7 billion by 2032 (Kings Research, via Shopify Aug 2026)
[!unverified] 92% of Gen Z shoppers want AR when shopping (Snap, 2026); 61% of consumers prefer retailers offering AR (NielsenIQ, 2026) — cited by Frame Sixty (Aug 2026) but original survey methodology not confirmed.
Shopify implementation
Shopify natively supports GLB for Android AR: uploading both a GLB and USDZ to a product page enables auto-detection and device-appropriate serving of the correct format. No additional code is required for Shopify merchants on Online Store 2.0. (Shopify Blog, Aug 2026)
Older Shopify themes (pre-OS 2.0) may not render <model-viewer> automatically and require a theme update. (Shopify Blog, Aug 2026)
2025–2026 updates
- model-viewer v4.3.1 (June 2025) — latest release; fixes shadows regression; v4.3.0 added
<extra-model>multi-model scenes, KTX2 texture API, iOS WebGL memory leak fix, AR Quick Look WKWebView transitions fixed (github.com/google/model-viewer/releases, fetched 2026-09-27) - model-viewer v4.0.0 (October 2024) — breaking change: default tone-mapping changed to PBR Neutral (use
tone-mapping="aces"to restore legacy behavior) (github.com/google/model-viewer/releases, fetched 2026-09-27) - WebXR now default in model-viewer on Android, with Scene Viewer as fallback — reflects maturing Chrome WebXR support (developers.google.com/ar/develop/webxr/model-viewer, fetched 2026-09-27)
- ARCore SDK targets Android API 36 / 37 as of 2026; core Scene Viewer deep-link interface unchanged (developers.google.com/ar/whatsnew-arcore, fetched 2026-09-27)
- Samsung Internet 24.0.3.2 beta (2025) — restored WebXR immersive-ar session functionality after regression (browser compatibility research, 2026-09-27)
- Android XR (headset platform) — separate documentation under
developer.android.com/develop/xr/; distinct from mobile Scene Viewer (developers.google.com/ar/develop/scene-viewer, fetched 2026-09-27)
Practitioner gotchas
- Intent URL only works reliably in Chrome on Android — Samsung Internet and Firefox will not handle the raw intent URL; use
<model-viewer>as the abstraction layer (web synthesis, 2026-09-27) - Scene Viewer launches as a separate app — user must navigate back manually; ecommerce flows (add-to-cart, wishlist) are not accessible during the AR session (developers.google.com/ar/develop/webxr/model-viewer, fetched 2026-09-27)
- USDZ and GLB can render materials differently — always QA on physical iOS and Android devices (Frame Sixty, Aug 2026)
- GLB file above ~15 MB may fail to load or create unacceptable delays on mobile networks (Frame Sixty Aug 2026; web synthesis)
- AI-generated GLBs (Neural4D, Tripo3D, Meshy.ai) produce base meshes in minutes but production hero assets still need human retopology for quality and file-size targets (Frame Sixty Aug 2026)
Key terms
| Term | Meaning |
|---|---|
| GLB | Binary glTF 2.0 — single-file 3D format required by Scene Viewer |
| Intent URL | Android deep-link URL scheme used to launch Scene Viewer from a browser |
| ARCore | Google's AR platform; provides SLAM tracking, surface detection for Scene Viewer |
<model-viewer> | Google open-source web component that wraps Scene Viewer + WebXR + Quick Look |
ar-modes | model-viewer attribute controlling AR mode priority: webxr, scene-viewer, quick-look |
| Draco | Google compression library for glTF geometry — reduces file size ~5:1 |
| KTX2 / Basis Universal | Texture compression formats for glTF — GPU-native, reduces texture payload |
3d_preferred | Default Scene Viewer mode — starts in 3D, user can opt into AR |
ar_only | Scene Viewer mode — AR experience, no 3D fallback |
Frontier links: ARKit · Object Capture · Spatial Commerce · glTF (GL Transmission Format) · USDZ · KHR_interactivity · Meshy.ai · Tripo3D · Android XR · 8th Wall
Sources: Web — Android Scene Viewer 2026-09-27 · Registry — Android Scene Viewer 2026-09-27 · YouTube — Android Scene Viewer 2026-09-27