Add Android XR docs

keveleigh · keveleigh · commit ea60a71dbf95 · 2025-12-04T16:32:01.000-08:00
diff --git a/docs/mrtk3-overview/getting-started/setting-up/setup-new-project.md b/docs/mrtk3-overview/getting-started/setting-up/setup-new-project.md
@@ -67,8 +67,9 @@ Once imported, MRTK3 requires a profile to be set for the standalone target plat
 
 Once imported, MRTK3 requires some configuration on OpenXR if you're targeting a specific XR device. Refer to the instructions on the following pages for platform-specific guidance.
 
-- [Deploy to a Quest device](../../test-and-deploy/quest-deployment.md#deployment-prerequisites)
-- [Deploy to HoloLens 2](../../test-and-deploy/hololens2-deployment.md#deployment-prerequisites)
+- [Deploy to an Android XR device](../../test-and-deploy/android-xr-deployment.md)
+- [Deploy to a Quest device](../../test-and-deploy/quest-deployment.md)
+- [Deploy to HoloLens 2](../../test-and-deploy/hololens2-deployment.md)
 
 ### 6. Congratulations, the project setup is now finished
 
diff --git a/docs/mrtk3-overview/images/android-xr-openxr.png b/docs/mrtk3-overview/images/android-xr-openxr.png
diff --git a/docs/mrtk3-overview/test-and-deploy/android-xr-deployment.md b/docs/mrtk3-overview/test-and-deploy/android-xr-deployment.md
@@ -0,0 +1,57 @@
+---
+title: Deploy to an Android XR device
+parent: Test and experience overview
+nav_order: 2
+---
+
+# Deploy to an Android XR device
+
+This page describes how to deploy your Unity Project with MRTK3 onto an Android XR device.
+
+> [!NOTE]
+> For general Android XR and Unity information, see the [Android XR developer docs](https://developer.android.com/develop/xr/unity).
+
+## Deployment Prerequisites
+
+1. Add MRTK to your project and ensure your [project settings](../getting-started/setting-up/setup-new-project.md#5-configure-openxr-related-settings) are configured correctly to use the OpenXR pipeline and MRTK's feature set. **These features are required to deploy your project onto your Android XR device**.
+
+    > [!NOTE]
+    > If starting from the [template project](../getting-started/setting-up/setup-template.md), these project settings should already be configured for you.
+
+1. Navigate to **File > Build Settings**.
+
+1. Under **Platform**, select **Android**. Switch the platform to **Android**, and wait for the operation to finish.
+
+1. Navigate to **Edit > Project Settings**.
+
+1. Under **Project Settings**, navigate to **XR Plug-in Management** and enable **OpenXR** under the **Android** tab. Ensure that **Initialize XR on Startup** is selected and that no feature groups are enabled, and wait for the operation to finish.
+
+    ![Android XR Plug-in Management window](../images/android-xr-plug-in-management.png)
+
+    > [!NOTE]
+    > A yellow warning icon may appear after checking the **OpenXR** option. Click that icon to open the **OpenXR Project Validation** tool. Click **Fix All** and ignore the interaction profile issue that can't be auto-fixed. The profiles will be added in the step below.
+
+1. Under **Project Settings**, navigate to **XR Plug-in Management > OpenXR > Interaction Profiles** and ensure the following profiles are listed based on the MRTK features you'd like to use:
+
+    | Profile | MRTK |
+    |---------|------|
+    | Hand Interaction Profile | For articulated hand input |
+    | Oculus Touch Controller Profile | For controller input |
+
+1. Under **Project Settings**, navigate to **XR Plug-in Management > OpenXR > OpenXR Feature Groups** and ensure the following features are checked under **All Features** based on the MRTK features you'd like to use:
+
+    | Feature | MRTK |
+    |---------|------|
+    | Android XR: AR Session <br> Android XR: Hand Mesh Data | For rendering the system hand mesh |
+    | Hand Tracking Subsystem | For rendering the articulated hand joints |
+
+    ![Android XR OpenXR](../images/android-xr-openxr.png)
+
+    > [!NOTE]
+    > You can enable additional features as needed, but in-scene support for them will come from other packages, like AR Foundation.
+
+1. A yellow warning icon or red error icon may appear during this process. Click that icon to open the **OpenXR Project Validation** tool. Select **Fix All** to address the issues. There may be several items to address.
+
+## Deploying to Device
+
+1. After you have the project configured, proceed to [build and run the Unity Project](https://docs.unity3d.com/Manual/xr-run.html).
diff --git a/docs/mrtk3-overview/test-and-deploy/hololens2-deployment.md b/docs/mrtk3-overview/test-and-deploy/hololens2-deployment.md
@@ -16,7 +16,7 @@ This page describes how to deploy your Unity Project with MRTK3 onto a HoloLens
 1. Add MRTK to your project and ensure your [project settings](../getting-started/setting-up/setup-new-project.md#5-configure-openxr-related-settings) are configured correctly to use the OpenXR pipeline and MRTK's feature set. **These features are required to deploy your project onto your HoloLens**.
 
     > [!NOTE]
-    > If starting from our [template project](../getting-started/setting-up/setup-template.md), these project settings should already be configured for you.
+    > If starting from the [template project](../getting-started/setting-up/setup-template.md), these project settings should already be configured for you.
 
 1. Navigate to **File > Build Settings**.
 
@@ -38,7 +38,7 @@ This page describes how to deploy your Unity Project with MRTK3 onto a HoloLens
     [![UWP XR Plug-in Management window](../images/uwp-xr-plug-in-management.png)](../images/uwp-xr-plug-in-management.png)
 
     > [!NOTE]
-    > A yellow warning icon may appear after checking the **OpenXR** option. Click that icon to open the **OpenXR Project Validation** tool. Click **Fix all** and ignore the interaction profile issue that can't be auto-fixed. The profiles will be added in the step below.
+    > A yellow warning icon may appear after checking the **OpenXR** option. Click that icon to open the **OpenXR Project Validation** tool. Click **Fix All** and ignore the interaction profile issue that can't be auto-fixed. The profiles will be added in the step below.
 
 1. Under **Project Settings**, navigate to **XR Plug-in Management > OpenXR > Interaction Profiles** and ensure the following profiles are listed based on the MRTK features you'd like to use:
 
diff --git a/docs/mrtk3-overview/test-and-deploy/overview.md b/docs/mrtk3-overview/test-and-deploy/overview.md
@@ -14,14 +14,15 @@ Compiling and deploying your app can take a significant amount of time, so we re
 - [In-editor input simulation](../../mrtk3-input/packages/input/input-simulation.md)
   - Easily preview your app without any XR device attached. Control the user's head, hands, and hand gestures with traditional WASD controls.
 
-- [Stream to a device](streaming.md)
+- [Stream to a device](./streaming.md)
   - These solutions allow you to run the app locally in the Unity editor in Play Mode and stream the experience to your device. All inputs from your device are sent to the PC, where the content is then rendered in a virtual immersive view. We highly recommend this solution for instant iteration and for showcasing prototypes
 
 ## Build and deploy
 
 The following guides will walk you through building and running your application on a device.
 
-- [HoloLens 2](hololens2-deployment.md)
-- [Quest Devices](quest-deployment.md)
+- [Deploy to an Android XR device](./android-xr-deployment.md)
+- [Deploy to a Quest device](./quest-deployment.md)
+- [Deploy to HoloLens 2](./hololens2-deployment.md)
 
 If you've deployed a build to your target device of choice, you can debug the build as it runs on device with [Managed debugging](https://learn.microsoft.com/windows/mixed-reality/develop/unity/managed-debugging-with-unity-il2cpp).
diff --git a/docs/mrtk3-overview/test-and-deploy/quest-deployment.md b/docs/mrtk3-overview/test-and-deploy/quest-deployment.md
@@ -19,10 +19,10 @@ These steps are based around OpenXR as your runtime (i.e. XR plugin provider) as
 
 1. Ensure that [developer mode](https://developer.oculus.com/documentation/native/android/mobile-device-setup/#enable-developer-mode) is enabled on your device (you may need to [join a developer team](https://developers.meta.com/horizon/documentation/native/android/mobile-device-setup/#joining-or-creating-a-team) first). Installing the Oculus ADB Drivers is optional.
 
-1. Add MRTK to your project and ensure that your [project settings](../getting-started/setting-up/setup-new-project.md#5-configure-openxr-related-settings) are configured correctly to use the OpenXR pipeline and MRTK's feature set. **These features are required to deploy your project onto your Quest device**. You may ignore project settings instructions regarding the UWP platform.
+1. Add MRTK to your project and ensure that your [project settings](../getting-started/setting-up/setup-new-project.md#5-configure-openxr-related-settings) are configured correctly to use the OpenXR pipeline and MRTK's feature set. **These features are required to deploy your project onto your Quest device**.
 
     > [!NOTE]
-    > If starting from our [template project](../getting-started/setting-up/setup-template.md), these project settings should already be configured for you.
+    > If starting from the [template project](../getting-started/setting-up/setup-template.md), these project settings should already be configured for you.
 
 1. Navigate to **File > Build Settings**.
 
@@ -35,14 +35,14 @@ These steps are based around OpenXR as your runtime (i.e. XR plugin provider) as
     ![Android XR Plug-in Management window](../images/android-xr-plug-in-management.png)
 
     > [!NOTE]
-    > A yellow warning icon may appear after checking the **OpenXR** option. Click that icon to open the **OpenXR Project Validation** tool. Click **Fix all** and ignore the interaction profile issue that can't be auto-fixed. The profiles will be added in the step below.
+    > A yellow warning icon may appear after checking the **OpenXR** option. Click that icon to open the **OpenXR Project Validation** tool. Click **Fix All** and ignore the interaction profile issue that can't be auto-fixed. The profiles will be added in the step below.
 
 1. Under **Project Settings**, navigate to **XR Plug-in Management > OpenXR > Interaction Profiles** and ensure the following profiles are listed based on the MRTK features you'd like to use:
 
     | Profile | MRTK |
     |---------|------|
-    | Oculus Touch Controller Profile | For controller input |
     | Hand Interaction Profile | For articulated hand input |
+    | Oculus Touch Controller Profile | For controller input |
 
 1. Under **Project Settings**, navigate to **XR Plug-in Management > OpenXR > OpenXR Feature Groups** and ensure the following features are checked under **All Features** based on the MRTK features you'd like to use:
 
