Device Readiness

Context

This skill prepares a Unity project for Meta VR Glasses device requirements across two dimensions: input (hand tracking as the primary input, not a fallback) and field of view (a device with a narrower FoV than current Quest headsets). The input workflow is immediately below; the field-of-view workflow is its own section further down.

The target device treats hand tracking as the primary input method, not a fallback. Most existing Quest projects were built controller-first, so the work isn't just "replace button presses with gestures" — it's rethinking interaction design so hands feel natural instead of like a worse controller. A systematic scan matters: find every controller dependency, understand the gameplay intent behind it, and map it to the right ISDK pattern.

When a Meta VR Glasses or Meta Quest device is connected, ground the audit in real device data first — metavr device list shows what's attached, and metavr device info <id> reports the device's input and display capabilities the audit should target.

Analysis Workflow

Step 1: Scan the Project

Build a complete picture of how the project handles input today. Controller dependencies hide in surprising places — not just obvious OVRInput.Get() calls, but also XR Interaction Toolkit components, Unity's legacy Input system, and custom grab systems. Cast a wide net: