About the project
Spatial Systems, Explained Clearly
Independent architecture guidance without pretending to be a live API service, official standard, or platform vendor.
An independent developer publication
SpatialAPI.xyz is an educational field guide for people designing software that represents, perceives, queries, reasons about, or renders space. The site covers spatial API architecture, AI and LLM tool design, AR and VR runtimes, maps and GPS, game engines, 3D delivery, devices, security, and privacy.
The site is not a hosted spatial API, a standards organization, a device vendor, a game engine company, or an official documentation mirror. Platform and standards names are used descriptively. Readers should verify implementation details against the current official documentation for the technology they use.
Editorial approach
Articles focus on durable architectural decisions: identity, coordinate frames, time, uncertainty, provenance, permission, portability, and lifecycle. Each journal article contains one editorial outbound link to an authoritative source that directly supports its subject. The rest of the article is original analysis and practical synthesis.
SpatialAPI.xyz does not publish fabricated benchmarks, testimonials, customer logos, rankings, partnerships, or claims that a product feature exists when it does not. Examples are illustrative and use invented identifiers rather than real personal or facility data.
Who the site is for
The material is intended for software architects, API designers, web and mobile developers, Unity and Unreal teams, geospatial engineers, XR developers, product managers, technical writers, privacy and security reviewers, and AI engineers building tools over images or scene data.
The guides are platform-aware but platform-neutral in structure. A team can start with a maps, AR, engine, or AI problem and follow the same core questions: what is the entity, which frame applies, when is the value valid, how certain is it, who may use it, and how does it survive across sessions and devices?
Contact and corrections
Questions, source corrections, accessibility feedback, and editorial notes can be sent to [email protected]. The site does not use a contact form, account system, or newsletter signup. Please do not send credentials, private location data, room scans, or other sensitive material by email.
When reporting a correction, include the page URL, the statement in question, and a primary source when available. Substantive corrections should update the page’s visible modification date and structured metadata.