The Problem WebAR Solved
To understand why WebAR mattered, you need to understand the distribution problem that every AR developer faced before it existed. Building an AR experience in 2015 or 2016 meant building a native app — iOS app, Android app, or both. That meant app store submission, approval wait times, version compatibility maintenance, and most critically, asking users to download something before they could experience anything.
For marketing campaigns, product launches, and brand experiences — the commercial contexts where AR made the most business sense — this friction was often fatal. Studies consistently showed that the majority of users who scanned a QR code linking to an app store download never completed the install. The experience was dead before it started.
Before WebAR: scan QR code → go to app store → download app (100MB+) → install → open app → find AR feature → experience. With WebAR: scan QR code → browser opens → AR starts. The difference in completion rate between these two flows was enormous — typically 60 to 80% drop-off reduction with WebAR.
The Two Platforms I Tested — 8th Wall and Wikitude
What Testing These Platforms Was Like
Testing 8th Wall and Wikitude gave me a clear sense of what WebAR could and could not do compared to native AR applications. The fundamental achievement was real — point a mobile browser camera at the world and get world-tracked AR without any download. That was genuinely impressive and the improvement in deployment friction was immediately obvious.
8th Wall — SLAM in the Browser
What stood out about 8th Wall was that it brought real SLAM tracking — simultaneous localisation and mapping, the same technology that powers ARKit and ARCore world tracking — into a mobile browser environment. Before 8th Wall, browser-based AR was mostly limited to image target recognition: scan a marker, get an overlay. 8th Wall's SLAM meant you could place 3D objects in the environment and walk around them, maintaining their position in real space — without an app.
The experience quality was noticeably below native ARKit or ARCore — frame rates were lower, tracking was less stable, and complex 3D scenes pushed mobile browsers to their limits. But for marketing and brand experiences where the content was relatively simple — a 3D logo, a product in your space, an animated character — it was more than capable enough. And the distribution advantage was enormous.
Wikitude — Veteran SDK With WebAR
Wikitude had a different character to it. Founded in 2008, it was one of the oldest AR SDKs in existence — it had been through the entire arc of mobile AR development, from GPS-based location AR in the early smartphone era through image tracking, SLAM, and eventually WebAR. Testing Wikitude felt like working with a platform that had accumulated years of real-world AR development experience. Its image tracking was mature and reliable. Its WebAR implementation offered JavaScript-based AR that could be embedded in web pages and triggered through standard web links.
Where Wikitude excelled was enterprise and tourism use cases — overlaying information on real-world locations, providing AR guides through museums and heritage sites, powering retail AR experiences through web browsers rather than dedicated apps. Its geographic AR capabilities — placing content at real-world GPS coordinates — were particularly strong, reflecting its roots in location-based AR from 2008.
Before and After WebAR — The Deployment Difference
- Client scans printed QR code
- Redirected to App Store or Play Store
- Must download app (50–200MB)
- Wait for install to complete
- Open app — find AR feature
- Grant camera permission
- Finally reach AR experience
- App remains on phone after use
- Developer maintains separate iOS + Android builds
- App store approval required for updates
- Client scans QR code
- Mobile browser opens directly
- No download required
- Grant camera permission
- AR experience starts immediately
- Single URL works on iOS and Android
- Updates deploy instantly — no approval
- Analytics via standard web tools
- Can be embedded in any webpage
- Share via any link or social media
What WebAR Was Used For
The Limitations WebAR Never Fully Solved
WebAR was genuinely transformative for distribution but it came with real limitations that native AR applications did not have.
- Performance ceiling — browsers cannot access hardware as directly as native apps. Complex AR scenes, high frame rates, and real-time effects hit browser performance limits that native applications handled smoothly.
- Tracking quality gap — SLAM tracking in a browser was never as stable or accurate as ARKit or ARCore. For experiences where precise tracking mattered — detailed product try-on, architectural visualisation — the gap was noticeable.
- iOS camera access restrictions — Apple restricted browser camera access in ways that created specific limitations for WebAR on iPhone. These restrictions eased over time but remained a friction point for years.
- No persistent AR — without native OS integration, WebAR could not access ARKit or ARCore's persistent anchor capabilities. Content could not be placed and returned to in the same real-world position across sessions.
WebAR in 2026 — Where It Stands Now
WebAR has matured significantly since its early days. The WebXR Device API — a browser standard that gives web applications access to native AR and VR capabilities — has brought ARKit and ARCore functionality closer to the browser. Modern WebAR experiences on supported devices can access plane detection, image tracking, and lighting estimation through the browser without the workarounds that 8th Wall and Wikitude originally needed.
8th Wall was acquired by Niantic — the company behind Pokémon GO — in 2022, signalling the strategic importance of WebAR for location-based experiences. Wikitude's technology was absorbed into Qualcomm's Spaces platform. The WebAR ecosystem has consolidated around a smaller number of more capable platforms, with the underlying browser standards catching up to what the pioneer platforms built through custom implementations.
Testing 8th Wall and Wikitude clarified something I had been thinking about for years — that the hardest problem in AR was never the technology. It was always the gap between what the technology could do and what a real user was willing to do to access it. WebAR did not make AR better. It made AR accessible. And in many commercial contexts, accessible beats better every time. An AR experience that reaches 10,000 people through a browser link is more valuable than an AR experience that reaches 300 people who downloaded a dedicated app. That lesson — that distribution is often more important than quality — applies beyond AR. It applies to almost everything in technology. The best technology that no one can reach does not change anything. Adequate technology that everyone can reach changes everything.
Frequently Asked Questions
What is WebAR and how does it work?
WebAR is augmented reality that runs directly in a mobile web browser without requiring any app download. It works by using the browser's camera access API to stream the live camera feed, then applying computer vision and 3D rendering in JavaScript to overlay AR content on that feed in real time. Platforms like 8th Wall built custom SLAM tracking implementations that ran entirely in JavaScript, while newer approaches use the WebXR Device API to access native AR capabilities through the browser on supported devices.
What happened to 8th Wall?
8th Wall was acquired by Niantic — the company behind Pokémon GO and Ingress — in March 2022. Under Niantic, 8th Wall continued as a WebAR platform and was integrated with Niantic's Lightship platform for location-based AR experiences. The acquisition reflected Niantic's strategic interest in making AR accessible without app downloads, complementing their existing location-based gaming infrastructure.
What happened to Wikitude?
Wikitude, founded in 2008 and one of the oldest AR companies in existence, was acquired by Qualcomm in 2021. Its technology was integrated into Qualcomm's Snapdragon Spaces platform — Qualcomm's XR developer ecosystem for headsets and glasses. The Wikitude brand was effectively retired as a standalone product, though its core technology continues within the Qualcomm ecosystem targeting enterprise and wearable AR rather than its original mobile and WebAR focus.
Is WebAR still relevant in 2026?
Yes — WebAR remains highly relevant, particularly for commercial and marketing AR experiences where distribution reach matters more than tracking precision. The WebXR Device API has improved browser-based AR quality significantly, and platforms built on it can now access ARKit and ARCore capabilities through the browser on supported devices. For brand activations, retail try-on, product packaging AR, and event experiences, WebAR's frictionless distribution continues to make it the preferred approach over native apps.