Onirix Web AR Player
Onirix Web AR Player allows you to display complete AR experiences in a web browser.
Prepare your experience with some models and interaction, and share instantly with your audience in a frictionless way.
Try yourself: webAR example
Take a look at this sample experience to test the use of webAR with image tracking through your mobile browser. First, check out this video, this is the experience you should see using the following example:
Now try yourself by detecting the QR code to launch the experience, and then detecting the image of the poster to make it come alive (click the image to view close-up):
Compatibility
Onirix Web AR Player is compatible with the following mobile web browsers:
| OS | Version | Supported browsers |
|---|---|---|
| iOS | iOS 11+ | Safari, Chrome, Safari view controller (SFViewController): iOS 13+, Safari web views (WKWebView): iOS 14.3+ |
| Android | Any | Chrome, Firefox, Samsung Internet, Edge, native android web views (Android 4.4+) * |
*Other browsers may be also compatible if supporting the following capabilities: WebGL, CameraAPI, DeviceMotionAPI, WebAssembly (WASM).
Devices must also conform to the following hardware requirements:
- Rear camera with at least VGA resolution (640x480px)
- Gyroscope sensor (only required for surface scenes).
- 2 GB RAM
According to statcounter analytics, this means a global 94,29% worldwide browser compatibility.
Regarding to performance, take a look at the following table with some real devices to have an idea of performance for each device tier:
| Device | Hardware | Performance |
|---|---|---|
| iPhone 12 | A14 Bionic | Very High |
| Asus Zenfone 9 | Snapdragon 8+ Gen 1: High-end, latest generation, powerful CPU and GPU (Adreno 730) | Very High |
| Oppo Find X2 | Snapdragon 865: High-end, slightly older than Snapdragon 8+ Gen 1, but still very powerful (Adreno 650) | Very High |
| iPhone 8 | A11 Bionic | High |
| Honor 70 | Snapdragon 778G+: Upper mid-range, good balance of performance and efficiency (Adreno 642L) | High |
| Huawei Mate 20 | Kirin 980: High-end chip from a few years ago, still decent for many tasks (Mali-G76 MP10) | High |
| Google Pixel 2 XL | Snapdragon 835: High-end, now relatively outdated, slightly older than Snapdragon 865 (Adreno 540) | Moderate to High |
| Huawei Mate 9 | Kirin 960: Older high-end chip, now relatively outdated (Mali-G71 MP8) | Moderate |
| Honor X7a | MediaTek Helio G37: Entry to mid-range, similar to Helio P35 in performance (PowerVR GE8320) | Low to Moderate |
| Samsung Galaxy A04 | MediaTek Helio P35: Entry-level, less powerful for high-demand tasks (PowerVR GE8320) | Low |
| Samsung Galaxy Tab A7 Lite | MediaTek Helio P22T: Entry-level, similar performance to Helio P35 (PowerVR GE8320) | Low |
Supported scene types and other limitations
Running in a browser has many advantages like avoiding app installations or the ability to embed experiences in existing web sites, but it also has some disadvantages compared with running on a native application.
The browser adds an extra layer of complexity, it is not the operating system who will directly manage your app resources, it will be your browser through the operating system, and this translates into about a 30% performance loss compared to the same experience on a native app.
It is really important not to overpass 3D model requirements to ensure a good performance in your experiences.
Take a look at the following table to check Android and iOS support for each scene type:
| Scene type | Android | iOS |
|---|---|---|
| Surface (Rotation-Tracking) | Supported | Supported |
| Surface (World-Tracking) | Supported (uses WebXR on compatible devices / browsers* and fallbacks to a custom tracking implementation if not available) | Supported (uses WebXR on certain browsers** and fallbacks to a custom tracking implementation if not available) |
| Image | Supported | Supported |
| QR Code | Supported | Supported |
| Spatial | Coming soon | Coming soon |
* Android browsers compatible with Web XR API currently are Google Chrome, Edge, Samsung Internet and other Chromium based browsers.
** Currently, iOS default browser (Safari) is not compatible with Web XR API. However you can use other browsers which have implemented it, like Mozilla XR Viewer.
Displaying single 3D assets
If you just want to share a single 3D asset without any interaction, Onirix Asset Viewer allows you to rapidly publish and share an asset, without needing to create a new project and associated scenes. Visit WebAR for Assets for more information.