XR / Spatial Computing

Apple Spent Two Years Insisting Vision Pro Didn't Need Controllers. It Just Published 74 Pages on How to Build Them.

visionOS 27's third-party motion controller framework defines a spatial accessory as an LED constellation, an IMU, and a Bluetooth radio — tracked at up to the headset's full display rate — and Apple is already working with DFRobot and MIKROE on reference hardware.

Apple has published detailed technical specifications for third-party motion controllers on Vision Pro, formalizing support it introduced with visionOS 27 for tracked “spatial accessories.” It’s a notable reversal in tone: Apple spent roughly two years positioning hand and eye tracking as the deliberate, sufficient input model for Vision Pro, treating the absence of controllers as a feature rather than a gap. The new spec doesn’t walk that framing back exactly, but it does hand the job of building physical controllers to the accessory market rather than doing it in-house.

Watch: Apple Vision Pro — Hands-On (YouTube)

What actually counts as a spatial accessory

The specification defines a spatial accessory as an active electronic device built from three required components: a constellation of infrared LEDs for optical tracking, an IMU chip for positional and orientation data, and a Bluetooth connection back to the headset. Buttons and haptic feedback are explicitly optional, which keeps the baseline requirement relatively low-cost while leaving room for more elaborate controllers further up the market. VisionOS 27 tracks these accessories using the known IR LED pattern combined with IMU data streamed over Bluetooth, and Apple says tracking can run up to the display’s native refresh rate — nominally 90Hz, with headroom toward 120Hz.

Apple is seeding reference hardware, not shipping its own

Rather than releasing an Apple-branded controller, the company is working with DFRobot and MIKROE to produce off-the-shelf trackers explicitly positioned as reference hardware and development kits — components meant to give accessory makers, and hobbyists building their own tracked objects, a known-working starting point rather than a from-scratch electronics project. That’s a meaningfully different go-to-market than a first-party controller launch: it puts Apple in the position of standard-setter and technical enabler rather than competing directly with whatever the accessory ecosystem eventually produces.

Why this matters for anyone building on Vision Pro

For creative technologists, the interesting part isn’t gaming input parity with Quest — it’s that visionOS 27 just defined a reasonably accessible, well-documented path to building custom tracked physical objects that a Vision Pro can locate in space at high frame rates. That’s a primitive generative artists, installation builders, and instrument makers have wanted since Vision Pro launched: a way to bring a real, tangible object into a spatial-computing scene with tracking fidelity that doesn’t depend on the headset’s cameras seeing it clearly. Kickstarter campaigns for third-party controllers built against this spec have already started appearing, well ahead of any first commercial products actually shipping.