Web 3D & AR: what it’s actually good for (and what it isn’t)

Interactive 3D and browser-based AR are one of the few things that still make a web product feel genuinely new. They are also one of the easiest ways to burn a budget on something nobody uses. Both are true at once.

Where it genuinely earns its place

The pattern that consistently pays off is removing a real purchase or comprehension barrier — letting someone see a product the way they would in person before they commit.

• Product viewers where size, material or finish actually drives the decision — furniture, hardware, fashion
• Configurators where a customer builds their variant and sees it instantly
• “View in your space” AR for anything bought based on how it fits a real room
• Explaining a complex physical or spatial concept that words and flat images fail at

Where it is just expensive decoration

A spinning 3D logo on a landing page. A heavy scene that adds seconds to load and nothing to the decision. Spatial features bolted on because a competitor has one. If a 2D image would convey the same thing, a 3D scene is usually a slower, costlier way to convey it.

The question is never “can we build it in 3D?” It is “does seeing this in space change what the user does next?”

The part teams underestimate

Performance and graceful degradation are the actual hard problems, not the visuals. A 3D feature that janks on a mid-range phone or fails silently without WebGL is worse than no feature at all. Done right, it is hardened, it falls back cleanly, and it stays fast — which is exactly the boring engineering work that makes the impressive part trustworthy.

This is our specialty, so we will keep writing about the engineering of it here — honestly, including the trade-offs.