Spatial Computing Studio
Internal-facing reference we share with learners — three pillars that gate every review.
Spatial UX rules
- Arm-length legibility beats monitor-perfect kerning.
- Every interactive surface names its fallback when tracking drops.
- Passthrough features ship with a written data refusal list.
- Audio buses get as much budget discussion as draw calls.
Prototype loop
Sketch constraints → greybox in engine → capture → mentor markup → retro note → repeat. No step may be skipped, even when deadlines hiss.
Performance budget
Each module publishes CPU/GPU/audio targets. Exceeding them is allowed for experiments — shipping without documenting why is not.