Monitor Active Content
Monitor what content apps are actively running on devices. The name of the active content app will be displayed beneath the device’s battery, WiFi, and storage space icons.
See the latest feature releases, product improvements, and bug fixes.
Monitor what content apps are actively running on devices. The name of the active content app will be displayed beneath the device’s battery, WiFi, and storage space icons.
ArborXR has moved to a side navigation menu and has introduced Tags and Organization Settings as menu options.
This product improvement allows you to go into the “Manage Organizations” page and set a default organization as well as change the order of your organizations.
Multi-App Launcher is a 2D app launcher that displays a grid of content apps installed via ArborXR that have been “whitelisted” via the dashboard. This allows end users to launch into content themselves while preventing them from accessing other apps installed on the device.
Add release notes to each version of your content app and view other information such as the versionName, versionCode, and the filename of the APK and any corresponding expansion files, such as an OBB file.
With this improvement users can upload an OBB file alongside their APK. When users deploy a content app that contains an OBB onto a device, the OBB will automatically be deployed alongside the APK. Note that the APK and its associated OBB must be in the same zipped folder in order for ArborXR to process the upload.
Content sharing enables you to easily share content apps between organizations you are a part of with just a few clicks. This saves you the hassle of uploading the same content app into every organization you are a part of.
Multi-Organization functionality enables you to create multiple organizations and easily toggle between them, thereby allowing you to securely group devices, content apps and users.
This product improvement is relevant for users with multiple device types. If a user selects multiple devices, and if multiple device types are represented in their selection, users will be prompted to edit device settings (like Kiosk Mode) on a per device type basis. For example, users will manage device settings for Pico Neo 2 separately from managing device settings for Oculus Quest.
This product improvement is relevant for users with multiple device types and ensures users deploy content apps to the correct device types. For example, this will prevent a content app built for Pico Neo 2 from being deployed onto an Oculus Quest.