Unity PolySpatial

Snapshot Verdict

Unity PolySpatial is a specialized bridge for developers wanting to bring existing 3D content and workflows into the visionOS ecosystem, specifically for the Apple Vision Pro. It is not a standalone app but a sophisticated toolkit that allows Unity-based applications to run natively in "Shared Space" alongside other visionOS apps. For developers, it is an essential but demanding gateway to spatial computing. For everyone else, it is the invisible engine that determines whether Vision Pro games look like high-end experiences or clunky ports. It excels at maintaining visual fidelity while navigating Apple’s strict privacy and processing constraints, though it requires a significant shift in how developers think about hardware input and rendering.

Product Version

Version reviewed: Unity 2022 LTS with visionOS Support (PolySpatial 1.1)

What This Product Actually Is

Unity PolySpatial is a technology suite designed to solve a specific problem: Apple’s visionOS does not allow third-party engines to have direct, "bare metal" access to the camera feed or the underlying hardware for privacy and battery reasons. Instead, Apple uses a proprietary rendering engine called RealityKit.

PolySpatial acts as a translator. It takes 3D data, materials, and shaders created in the Unity Editor and converts them in real-time into a format that RealityKit can understand. This allows Unity apps to run in the "Shared Space" of the Vision Pro, meaning a developer can place a 3D board game on a user’s physical coffee table while the user still sees their calendar, messages, and other native visionOS windows floating nearby.

Without PolySpatial, Unity developers would be limited to "Full Space" (Exclusive Mode), where the app takes over the entire field of view and cuts the user off from other apps. PolySpatial is the key to creating "mixed" experiences that feel integrated into the user's actual room rather than a digital void.

Real-World Use & Experience

Using PolySpatial feels like a tug-of-war between two different philosophies. On one side, you have Unity’s flexible, object-oriented workflow that developers have used for over a decade. On the other, you have Apple’s highly controlled, polished, and restricted RealityKit environment.

When you first open a project with PolySpatial, the experience is familiar. You see your 3D assets and your hierarchy. However, the moment you attempt to use standard features—like custom shaders or certain physics interactions—the friction begins. Because PolySpatial must "bake" your Unity content into RealityKit, you cannot use every trick in the book. You are forced to use the PolySpatial Lighting Model and specific shader graphs that Apple’s hardware can process.

The "Play to Device" feature is the highlight of the workflow. During development, you can stream your project directly to an Apple Vision Pro headset. Seeing your 3D objects appear on your desk almost instantly is a powerful moment. However, the iteration loop is slower than standard game development. You are constantly checking the "PolySpatial Hub" within Unity to see if your materials are compatible or if you’ve used a component that RealityKit will simply ignore.

Interaction is the biggest adjustment. Vision Pro relies on eyes and hands (look and pinch). In PolySpatial, you don't just write a script for a mouse click. You use the visionOS input system, which translates your hand pinches into "World Space" events. It works surprisingly well, but converting an existing VR game built for controllers into a PolySpatial project often requires rewriting the entire interaction layer from scratch.

Standout Strengths

• Enables shared space multi-app multitasking.
• Real-time preview on Vision Pro hardware.
• High-fidelity material translation to RealityKit.

The primary strength of PolySpatial is the ability to coexist. Most VR headsets are "one app at a time" devices. PolySpatial allows Unity developers to build tools and widgets that sit on a desk or hang on a wall while the user performs other tasks. This opens up a new category of "ambient" computing that didn't exist for high-end 3D engines previously.

Secondly, the visual quality is remarkably consistent. While you lose some of Unity's more experimental rendering features, the materials that do make it through the translation look excellent. Apple’s RealityKit handles grounding shadows and lighting with the physical room automatically, and PolySpatial ensures Unity objects receive that same treatment.

Finally, the cross-platform potential is significant. If you build a game using PolySpatial correctly, you are essentially building a project that can be deployed to visionOS while maintaining the core logic for Meta Quest or PCVR. It reduces the "silo" effect of Apple’s ecosystem by letting you keep the majority of your codebase in C# and Unity.

Limitations, Trade-offs & Red Flags

• Custom shaders require complex manual conversion.
• Expensive Unity Pro subscription requirement.
• Restricted access to raw camera data.

The biggest limitation is the "RealityKit Wall." If you have spent years perfecting custom HLSL shaders for your game, PolySpatial will likely break them. You are forced to use Unity’s Shader Graph, and even then, only a subset of nodes are supported. This can lead to a "homogenized" look where many PolySpatial apps start to look visually similar because they are all using the same approved Apple rendering paths.

Then there is the cost. To access the visionOS build support, including PolySpatial, you must have a Unity Pro, Enterprise, or Industry subscription. For an individual hobbyist or a small indie team, this is a significant recurring financial barrier. You cannot simply download "Unity Personal" and start building for the Vision Pro.

The privacy restrictions also create functional hurdles. Because PolySpatial apps run in the Shared Space, they do not get raw access to the user's hand skeletons or the room's mesh data in the same way an exclusive app does. You get "events"—a user pinched here, or looked there—but if your app requires precise, raw sensor data for a complex mechanic, PolySpatial might not be the right choice.

Who It's Actually For

PolySpatial is strictly for developers and technical artists. It is not for someone looking to "play" with AI or build a quick 3D model. If you are a professional developer tasked with bringing a corporate training tool, a tabletop game, or a productivity app to the Apple Vision Pro, this tool is mandatory.

It is also for companies that have a massive existing library of Unity assets. If you have five years of 3D content and you want to see it on a $3,500 headset without rebuilding it in Apple’s Xcode and Reality Composer Pro, PolySpatial is the only viable path. It is a "pro" tool for a "pro" device.

Value for Money & Alternatives

Value for money: fair

The value proposition is entirely dependent on your business model. If you are building a commercial product for the Vision Pro, the cost of Unity Pro is a necessary overhead. The time saved by not having to learn Swift and RealityKit from scratch is worth thousands of dollars in development hours. However, for a casual explorer, the entry price is too high.

Alternatives

• Native RealityKit/SwiftUI — The "Apple way" which offers better performance and smaller app sizes but requires learning an entirely new programming language and ecosystem.
• Unity (Full Space Mode) — Building a standard VR app in Unity without PolySpatial. It's easier to port but locks the user into your app and hides all other windows.
• Godot Engine — An open-source alternative that is developing visionOS support, though it lacks the tight integration and maturity of the Unity-Apple partnership.

Final Verdict

Unity PolySpatial is a remarkable piece of engineering that bridges a massive gap between the world's most popular game engine and Apple's premium spatial hardware. It is not a "magic button" that converts games instantly; it requires careful navigation of Apple’s constraints and a willingness to rethink graphics and input. While the subscription cost and rendering limitations are frustrating, it remains the most powerful way to create sophisticated, multitasking 3D applications for the future of spatial computing. If you are serious about the Vision Pro, you are likely already using it.