READ THE BODY.UNDERSTAND THE MOVE.
Natural play is built on deliberate boundaries. Explore the technology that connects the camera to game input.
Camera
Observe a frame containing body movement.
POSE CAPTUREApple Vision / MediaPipe / IPoseProvider
Read a person in the camera frame as joint coordinates. Apple Vision and the MediaPipe research implementation share a provider-neutral pose boundary.
Read the technical docs ↗BODY GEOMETRYCalibration / Image-plane geometry
Shoulder width and torso length establish body-relative references. The V3 research path uses coordinates corrected for the image aspect ratio.
Read the technical docs ↗MOTION INTENTC# / Temporal evidence / State machines
A single-frame shape is not the whole decision. Temporal evidence, current state and rearm conditions work together. Legacy, V3 and Demo Assist are distinct paths.
Read the technical docs ↗GAME RUNTIMEUnity / C# / Native iOS / IL2CPP
Recognized actions connect to the Unity game’s existing input boundary. Native camera ownership and managed code are separated by a bounded latest-frame bridge.
Read the technical docs ↗EVIDENCE & QADeterministic fixtures / Unity tests / Human acceptance
Automated tests, editor execution, device runtime and human physical acceptance provide different evidence. Current implementation does not imply release acceptance.
Read the technical docs ↗THE ENGINEERINGUNDER THE PLAY.
Architecture, equations and implementation evidence. A technical reference for the people building PhiMotion.
Explore Engineering Docs↗