There is a specific kind of naming mistake that only becomes visible in retrospect. A company picks a term that feels current, builds brand equity around it, and then watches the industry quietly abandon that term for something adjacent. The product is the same. The domain is the same. But the name now reads as a marker of a moment that has passed.
Spatial computing is in the middle of exactly that instability — and founders building in that space are making permanent naming decisions inside a temporary vocabulary.
The term problem is real and it's accelerating
"Metaverse" had a window of roughly eighteen months where it seemed like the organizing term for the 3D internet. Then it became a punchline. Companies that had built around it — in their names, their decks, their domain registrations — either pivoted the language quietly or lived with the association.
"Spatial computing" is the current replacement. Apple's adoption of it with Vision Pro gave it legitimacy and runway. But it is still a descriptor of what the technology does, not what it is to users. That's a meaningful distinction. Descriptive terms are useful for early market education; they tend to get replaced by more specific, use-case-driven vocabulary once the market segments.
Watch what's already happening. "Extended reality" gave way to XR, which is now mostly used by enterprise and defense contexts. "Immersive" has drifted toward entertainment and training verticals. "Volumetric" is technical and narrow. None of these terms have converged. That's the signal.
What this means for domain strategy
If you are building a spatial computing company and you register a domain built around a descriptor — spatial, immersive, volumetric, extended — you are making a bet on term stability that the last five years do not support.
This is not an argument against owning those domains. There is a real case for holding exact-match descriptive domains in a vocabulary that is still forming, because whoever ends up owning the winning term owns significant organic traffic and recall. The spatial computing portfolio at Domainnado reflects exactly this thesis: positions across several competing terms rather than a single bet.
But if you are a founder naming a company, the calculus is different from a domain investor's. You need a name that does not require the industry to settle on your preferred term for it to make sense. That argues for names that are either purely brandable and term-agnostic, or names tied to a specific function — navigation, rendering, presence, anchoring — rather than the broader category.
The anchor problem
One vocabulary pattern worth watching: spatial computing's core technical challenge is anchoring digital objects to physical space persistently and accurately. The term "anchor" is already used across Apple's ARKit, Microsoft's Azure Spatial Anchors, and various developer tools. It's a functional word that describes something real, and it has not yet been claimed at the brand level by any dominant consumer company.
Compare that to "presence" — which sounds compelling for a spatial brand but has been diluted across video conferencing, VR hardware marketing, and general tech copy to the point of near-meaninglessness.
Founders should be doing this kind of term archaeology before they name. Which words describe a specific function? Which are already claimed? Which are polluted by adjacent use? The answers change quickly in a market where the vocabulary isn't fixed.
The practical takeaway
For domain investors: the spatial category is one where portfolio breadth across competing terms makes more sense than depth in any single one. The winner hasn't been declared.
For founders: name to the function, not the category. If the category term disappears from common use in three years — and there's a reasonable chance it does — your company name should still parse.
The 3D internet is coming. What we're going to call it is genuinely unresolved. That uncertainty is a risk for founders and an opportunity for investors, but only if you understand which role you're playing.