The browser address bar has been with us for thirty years. It is unglamorous, barely noticed, and one of the most successful navigation primitives ever built. You type something, you land somewhere. Everyone understands it.

Spatial computing is quietly dismantling that primitive, and nobody has agreed on what replaces it.

The problem is not the headset

Most coverage of XR naming focuses on hardware brands — who owns the word "mixed reality," whether "metaverse" is recoverable after its association with a failed consumer push, and so on. That is a reasonable conversation, but it misses a more structural issue: inside a 3D environment, the concept of a URL becomes awkward.

A webpage is flat. It has one address, and that address maps cleanly to a document. A persistent spatial environment has rooms, objects, layers, and anchors — all of which may need to be addressable independently. If a user wants to share the exact corner of a virtual showroom where a product demo plays, what do they send? A screenshot? A timestamp? A deep link that requires the recipient to have the same app installed?

This is not a hypothetical. Enterprise XR deployments already run into this. A training simulation, a remote collaboration workspace, a virtual inspection of industrial equipment — each of these needs a way to say "go here, specifically." The platforms handling this today do it inconsistently and proprietarily.

Why naming conventions lag the hardware

Hardware cycles are fast because silicon roadmaps are measurable. Naming conventions are slow because they require consensus across competitors who have no incentive to cooperate early.

Consider how long it took the early web to standardize around .com as the default trust signal. Or how the mobile era produced a decade of competing deep-link schemes before universal links became a workable norm. Spatial computing is at a similar moment, except the address space is three-dimensional and the sessions are persistent, which makes the problem harder.

The vocabulary is still forming. Terms like "spatial anchor," "world-locked content," "scene graph," and "volumetric layer" each describe addressable concepts, but none of them have a clean consumer-facing shorthand yet. That gap — between technical precision and usable language — is where naming decisions get made by default rather than by design.

What this means for domain strategy

When a technology category lacks settled vocabulary, two things happen simultaneously: exact-match domains for technical terms become available longer than they should be, and brandable names have more room to define the category.

For investors watching the spatial computing space, the interesting domains right now are not "metaverse" variants — that ship has sailed — but the infrastructure layer. Terms related to spatial addressing, persistent session management, and location-sharing within 3D environments are still largely unclaimed at the premium level. Compare this to the AI agent space, where audit and session vocabulary got competitive fast once protocol discussions became public; spatial infrastructure naming is roughly two years behind that curve.

For founders building in XR, the lesson is simpler: if your product handles navigation, sharing, or addressing inside a spatial environment, your domain name should be legible without the product explanation. If you have to describe what the company does before someone can connect it to the name, the name is costing you something.

The anchor point

The web solved the URL problem once, imperfectly but well enough. Spatial computing will solve its equivalent — the question is whether the companies building those solutions are thinking about the naming layer now or after the vocabulary has been set by someone else.

The address bar survived thirty years not because it was elegant but because it was consistent. Whatever replaces it in 3D environments will have the same requirement. Consistency requires a shared vocabulary, and shared vocabularies begin with names.

Browse the spatial portfolio or the full domain index if you want to see what the naming layer looks like right now, before the conventions settle.