AR without an app: why the browser won

For most audiences, AR that requires an app install reaches almost no one — and AR that opens from a link reaches everyone. That single sentence settles a debate the industry spent years having. The technology behind native AR is genuinely better in places, but better technology that nobody opens loses to good-enough technology that everybody opens.

The browser won because it removed the one step that quietly kills participation: the install. Here's why that step matters more than any feature you could put behind it.

The install tax

Between "I want to try this" and "I'm looking at it," a native AR app charges a toll at every step. The person has to find the right app in a crowded store, download a few hundred megabytes, wait, open it, grant camera and motion permissions, then hunt for the specific feature inside an interface they've never seen. Each of those steps sheds people, and the losses compound — a chain where every link drops a fraction means only a sliver reaches the end.

For a one-time AR moment — a poster you scan once, a product you check on your floor before buying — that math is brutal. Nobody installs an app, learns it, and manages a fresh icon on their home screen for thirty seconds of payoff they'll never repeat. The effort dwarfs the reward, so they don't start. The experience can be flawless and it still loses, because almost no one gets far enough to see it.

A link goes where apps can't

A URL or QR code can live anywhere your audience already is. Print it on packaging, a poster, a shelf tag, a business card, a museum plaque. Drop it in an email, a social bio, a story, a text. Stick it on a sign in a window. Each of those is a doorway that opens straight into the experience.

An app can't do that. It lives behind a store listing, and the only thing you can put in the wild is a prompt to go install it — one more wall between intent and payoff. WebAR meets people on the surface they're already looking at, in the browser they already have open, with no detour through a store. The distribution surface is the entire physical and digital world, not a search box inside an app marketplace.

If your audience has to install something, most of them won't. Removing the install isn't a nice-to-have — it's the whole reason anyone shows up.

One build, every phone

Browser-based AR runs in the mobile browsers people already use — iOS Safari, Android Chrome — so there's no separate iOS and Android native build to maintain and no app-store review standing between a fix and your users. You publish once and it works across phones.

The runtimes underneath handle the differences for you. On capable Android devices, world and location tracking run on native WebXR and ARCore directly in the browser. Image, face and sky tracking run on the 8th Wall WebAR runtime, which also covers iOS, where browser AR is otherwise more limited. You don't manage any of that plumbing — you ship a scene, and it renders in a tab on either platform.

When native still wins

This isn't a claim that the browser beats native at everything — it doesn't. Persistent, high-fidelity, frequently-used experiences still belong in a native app. A game someone opens every day, a professional design or measurement tool, anything that needs dense meshes, console-grade lighting or anchors that survive across sessions: for those, the install is worth it, because the payoff is repeated and the fidelity is the point.

The honest line is about repetition and reach. If people will return to your experience daily and demand the highest fidelity, build native. If your goal is to put a moment in front of as many people as possible with the smallest possible barrier — a one-time or occasional experience tied to a campaign, a product, a place — the browser is the right tool. Most marketing, retail and event AR lives squarely in that second bucket. For a fuller comparison of how WebAR works and what it can track, see What is WebAR? Augmented reality that runs in the browser.

How XR Designer helps

XR Designer is built around link-first delivery. You compose a scene in a live viewport and publish it to a public link with an auto-generated QR code, optional password protection, and a branded splash screen — no app, no SDK, no engineering team. What you preview in the editor is exactly what ships, so there's no gap between the version you approved and the version your audience opens.

Because every experience is a link, you can also measure it like one. A per-experience analytics dashboard shows total opens, average time spent, and where visitors came from — QR, social, web, in-app or direct — so you can see which doorway is actually working. For a wider look at where this pays off, read 7 ways augmented reality grows your business.