If you are an OpenXR app developer working in Unity and you want the lowest-level control, this API will save you a lot of time otherwise spent on C# interop.

Unity will also depend on this native API for our own internal products, including future AR Foundation support for spatial entities.

@aras-p.bsky.social gave some great feedback last year that stuck with me:

"today [Unity] APIs are in a weird spot of being neither low level enough to be very flexible and performant, nor high level enough to be expressive and easy to use."

This release is a step toward low-level flexibility.

This is exactly what I want! Except an updated mount for Quest 3

My wish is for a 6DOF arm that can clamp to my desk, allowing me to suspend the headset in the air and move it around without it actually being on my head.

My setup needs some work tbh

I also have a need for more public and transparent C# ports of OpenXR API's. We're talking about it for sure, nothing to announce here yet.

"autogenerated" probably not a requirement for us at first.

I'm not personally involved on the graphics side, so I recommend that you post this question on Discussions to find the right person to answer

Register for XR Developer Night if you haven't yet! unityxrdevelopernightgdc2025.splashthat.com

If we have a remote role open up in the future I'll definitely post about it!

Unity's XR team is currently based in the US Pacific time zone. We have one role open right now but unfortunately they aren't accepting applications from outside the US for that one.

That said, our engineering team is active in Discussions every week if you want to post feedback there?

We aren't deprecating the Meta Quest Support feature but we are updating the loader that it uses.