Spatial AI APIs: Scene Understanding Without False Certainty
Design scene-understanding features that preserve context, confidence, and the distinction between inference and fact.
Read the field noteEXPLORE THE SPATIAL STACK / 04
Build scene-understanding features that preserve context, acknowledge uncertainty, and make bounded decisions.
Start with the decision the application needs to make. A decorative region suggestion, a placement aid, and a verified object identity are different goals. Do not use the broad promise of spatial intelligence to blur their evidence requirements.
The scene-understanding guide separates geometry, semantic predictions, and application decisions. It includes a documented vendor example with a limited scope, then develops an application-level workflow for uncertainty, evaluation, and correction.
For your own data contract, consider the source, timestamp, coordinate-space identifier, predicted category, confidence representation, and validity state. Document what these fields mean rather than presenting them as a universal API format.
A missing signal is not the same as an observed absence. A retained user choice is not the same as a current model prediction. Preserving these distinctions gives the application a useful response when observations are stale, incomplete, or in disagreement.
An application needs a way to decline an unsupported action without making the whole experience unusable. That may mean showing a suggestion rather than a commitment, asking for confirmation, or keeping an ordinary content view available.
Evaluate errors according to their consequences for the actual task. Separate false suggestions, missed opportunities, unstable transitions, and stale overlays. A single aggregate score can hide a problem that makes the product difficult to understand.
Keep data collection proportionate to the task. Identify what is processed, what leaves the device, and what is retained, then verify those statements against the deployed implementation before making privacy claims.
Read the depth guide for the geometric side of scene integration and Accessible XR for interaction flexibility. A spatial feature is more useful when people can understand its limits, correct its suggestions, and complete the task through an appropriate alternative path.

Design scene-understanding features that preserve context, confidence, and the distinction between inference and fact.
Read the field note
Use depth evidence thoughtfully, test visual boundaries, and preserve useful interactions when information is missing.
Read the field note
Make spatial tasks work through more than one input, viewpoint, or sensory channel, from session entry to exit.
Read the field noteStart with a clear foundation. Then build the experience your audience actually needs.
Explore the developer guides