dotnet-mixed-reality

To structure a mixed-reality app, apply architectural patterns that cleanly separate device-side MRTK and OpenXR responsibilities from Azure spatial and backend service integrations. This ensures maintainable Unity+C# client code.

For spatial anchors and spatial mapping in HoloLens apps, reference patterns provide ready-to-use code examples integrating MRTK and OpenXR. These examples streamline spatial awareness and device input implementation.

Yes, you can use this MRTK and OpenXR guidance for Unity+C# projects targeting shared experiences and remote rendering. Code examples cover these scenarios alongside hand menus, eye tracking, and QR tracking.

The best way to integrate Azure spatial services with .NET mixed-reality components is using provided reference patterns that ensure proper separation between client-side MRTK logic and Azure backend service responsibilities.

Yes, you need current MRTK and OpenXR tooling alongside Unity+C# and Azure service references to implement input actions and voice commands. These dependencies ensure valid spatial and device integration patterns.

Separating device-side and backend services when building mixed-reality solutions with MRTK and Azure prevents tightly coupled code. This architectural guidance ensures clean boundaries between client input handling and spatial backend processing.