Unity with visionOS

I brought reusable design-system patterns into hand-input prototypes, then tested tasks in a table scenario and extended the study to partner feedback. Hand occlusion and pinch-pointer affordance made the design question concrete: how do the hand, the target, and the response communicate one interaction? These studies formed part of the wider Unity XR foundation.

With engineering roadmaps and partner requirements pulling in different directions, I used concrete content to frame the platform: Window, Volume, and Space. That model had to hold beyond a diagram. Volume Chrome separated content, its boundary, and the controls that manage it; Remote Shell brought Player, Volume, Input, World, and Debug into one structure. The interface made an abstract spatial model inspectable through dimensions, positioning, input, and state.

My onboarding map followed creators from an idea through setup, configuration, development, testing, and delivery. Alpha feedback surfaced unsupported components. I led the Building Blocks working group to bring modular features, sample content, and the Editor workflow into an authoring concept organized around what creators were trying to do.

The interface required coordination across Authoring, Content, and Workflow. I brought those responsibilities into a combined proposal so navigation and the material behind it could evolve together. Building Blocks was a broader Unity XR initiative—the creator-tool foundation alongside the visionOS work.

I chose to keep the relationship between content, boundaries, and controls consistent across the headset and simulator, while adapting how people reach those controls. Testing revealed why this mattered: world-space controls were difficult to use, and overlapping windows forced people to keep rearranging their workspace. The design needed to help creators stay focused on their content as they moved between environments.

I explored controls that follow the user in the headset and a screen overlay in the simulator, weighing reachability and immersion against implementation effort and performance. For Beta, I prioritized a simpler, predictable experience: a static headset volume, with simulator mode switching deferred. The principle was to preserve a familiar spatial model while choosing controls suited to each environment.