Retailers in the GCC use augmented reality on phones for three jobs: letting shoppers try a product on or place it at home, guiding them to a shelf inside a store, and turning packaging into a screen. Most of this can run from a web link with no app install, using the 3D viewers built into iPhone and Android. A native app built on ARKit or ARCore is worth the extra cost when you need precise tracking, in-store navigation or a link to the loyalty account.
This guide explains each use case, what WebAR can and cannot do on today’s phones, and how to choose between a web experience and a native one.
What is AR in retail?
Augmented reality overlays digital content on the camera view of the real world. In retail, the content is usually a product: a sofa placed in a living room at true scale, sunglasses fitted to a face, or an animation that appears when the camera sees a package.
WebAR is AR that opens in the phone’s browser or built-in 3D viewer from a link or QR code. Native AR lives inside an app downloaded from the App Store or Google Play and uses Apple’s ARKit or Google’s ARCore directly.
What are the main AR use cases for retailers?
Three use cases account for most retail AR that reaches production.
- Virtual try-on and product placement: eyewear, cosmetics, watches and jewellery fitted to the shopper, or furniture and appliances placed in the room at real size. The business goal is confidence before purchase.
- In-store navigation: arrows and markers over the camera view that lead a shopper to a product, a promotion or a pickup counter. It depends on the phone knowing where it is inside the store, which needs a mapped space.
- Packaging and print: a QR code or the pack itself launches a 3D model, a recipe, a how-to or a competition. It turns owned media into a channel that can change after the product has shipped.
What can WebAR do on phones without an app?
The answer differs by platform, and the difference matters for planning.
On iPhone and iPad, the route for web AR is AR Quick Look. Apple states that built-in apps such as Safari, Messages, Mail, News and Notes use Quick Look to display USDZ files of virtual objects in 3D and AR, on devices running iOS 12 or later. Quick Look can also carry an Apple Pay button or a custom action banner, so a shopper can go from seeing a product in the room to checkout.
On Android, Google’s Scene Viewer does the same job for glTF and GLB models. Google lists the requirements as an ARCore-supported device running Android 7.0 or later, and it can be launched from a web page with a link or with the model-viewer web component.
For custom, interactive AR in the browser, the standard is the WebXR Device API from the W3C Immersive Web Working Group, a Candidate Recommendation Draft. Google documents that Chrome on Android uses ARCore to power WebXR AR sessions. MDN’s compatibility data, read in November 2026, shows no WebXR support in Safari on iPhone, and MDN marks the API as limited availability. In practice, a single web link has to serve Quick Look to iPhone and Scene Viewer or WebXR to Android.
When do you need a native ARKit or ARCore app?
Native AR gives direct access to the tracking features of the phone and to the rest of your app. Go native when the experience depends on one of the following.
- Accurate face or body tracking for try-on that must look right at the point of purchase. Google’s ARCore, for example, includes an Augmented Faces capability that also runs on ARKit-compatible iPhones.
- In-store navigation, which needs persistent mapping of the space and reliable positioning aisle by aisle.
- A signed-in shopper: loyalty points, saved sizes, wish lists and a basket shared with the rest of the app.
- Repeat use. A feature people open weekly belongs in the app they already have. A campaign people open once belongs on the web.
Native does not have to mean building twice. Unity’s AR Foundation is designed to create an AR app once and deploy it to both ARCore on Android and ARKit on iOS.
WebAR or native AR: how do they compare?
The table compares the two options criterion by criterion.
| Criterion | WebAR | Native app |
|---|---|---|
| Access | A link or QR code, nothing to install | Download from the App Store or Google Play |
| Reach | Anyone with a recent phone, including first-time visitors | People who already have or will install your app |
| Product placement | Strong, through Quick Look and Scene Viewer | Strong, with more control over lighting and interaction |
| Face and body try-on | Possible with specialist web libraries, quality varies by phone | Best tracking quality |
| In-store navigation | Limited | The practical choice |
| Checkout and loyalty | Hands off to the website | Shares the app’s account, basket and points |
| Best for | Campaigns, packaging, product pages | Features used repeatedly by known customers |
What does a retailer need before starting?
The largest cost in retail AR is usually the 3D catalogue, not the code. Each product needs an accurate, lightweight 3D model, exported as USDZ for Apple devices and as glTF or GLB for Android and the web. Decide early which products justify a model, who owns the files, and how they stay in sync with the product catalogue.
Then decide how success is measured. For try-on and placement, compare conversion and returns for shoppers who used AR against those who did not. For packaging, count scans and what people did next. Without that comparison, AR stays a demo.
Finally, treat the camera as personal data. Try-on processes a shopper’s face, and navigation processes their location in the store. Ask for consent in plain language, process on the device where possible, and keep nothing you do not need.
What does Eurisko X bring to retail AR?
We will be direct about our record. Eurisko X has no published AR project for a retail client. Our published AR work is Museum AR, an iOS and Android app Eurisko built for Deloitte in 2022: it uses an area target for indoor navigation, customises real-world objects in real time and opens a 3D portal through a real window. It is a museum app, not a store, but indoor navigation anchored to a mapped building is the technique the in-store navigation described above depends on. Our published retail work is the loyalty and commerce platform Eurisko built for Azadea Group, and our immersive retail product is the NextGen Metaverse Store, a VR store that continues the shopping journey across headset, TV, web and mobile.
What we offer for an AR project is the combination this work represents: a 3D and real-time team that builds in Unity and for the web, and a mobile and commerce team that connects the experience to catalogue, loyalty and payments. Eurisko X is the games and immersive studio of Eurisko, founded in 2009, with more than 200 in-house staff and offices in Adma, Riyadh, Dubai and Larnaca.
Sources
- Apple Developer, AR Quick Look (read November 2026)
- Google for Developers, Scene Viewer (read November 2026)
- Google for Developers, WebXR and ARCore (read November 2026)
- Google for Developers, ARCore supported devices (read November 2026)
- W3C, WebXR Device API, Candidate Recommendation Draft (November 2026)
- MDN Web Docs, WebXR Device API browser compatibility (read November 2026)
- Unity, AR Foundation manual (version 6.0)