XR Viewer Portable
- Last UpdatedDec 15, 2025
- 3 minute read
The XR Engine portable is a reduced version of the Windows-based XR engine. XR Engine portable is designed to run XR based application on portable devices, such as mobile phones or augmented reality devices.
The portable engine shares most of the code and the functionalities of the Windows engine with some exceptions and some specificity too. It supports a limited set of logical nodes and functionalities compared to Windows version. The List of nodes clearly states what is supported and what is not.
Write once and run anywhere
Developing an application for the portable platform follows exactly the same workflow as for the Windows platform. Everything is based on XR Studio, project templates, and XR scripts. Around 95% of the scripts designed for a portable application can run without any modification on the Windows platform. The remaining code can be enclosed into platform-dependent code snippets. Therefore, it is fairly easy to developing a project that can run on all platforms.
The presence of a Windows implementation of the portable engine also simplifies development and debug activities. The need of target devices can be limited to test platform specific functionalities.
Portable engine and its multiple target platforms
The XR Portable engine represents a common base. Each supported target platform represents a different specific implementation of the engine reflecting the capabilities and the functionalities of the target.
For this reason, there could be some differently supported functionality and even some platform-specific nodes.
Supported target platforms
The currently supported target platforms for XR Portable.
|
Target Platform |
Description |
|---|---|
|
This implementation can be used to debug the application directly inside XR Studio without the need to use the target device. |
|
|
Supports both iPhones and iPad devices. Provides advanced gesture and AR functionalities. |
|
|
Supports any modern Android tablet and smart phone. Provides advanced gesture and AR functionalities. |
|
|
Emulated environment that allows to test an app running inside a browser using the webassembly. |
XR Engine portable unique characteristics and differences compared to Windows version
A brief list of how the Portable engine application differs to a Windows version.
-
The config.xml configuration file is only partially supported. Even if this file is used to configure the portable engine, only a subset of its parameters are supported.
-
System fonts are not supported. The portable engine requires the font to be part of the project data. For more information, see Managing fonts.
-
Single PAK file deploy. Application must consist of a single PAK file. The PAK file must embed both module and project data.
-
Some specific texture pixel formats may be not supported. See Texture MipMaps.
Security Considerations for AVEVA XR Mobile
The AVEVA XR Mobile application stores PAK data and associated metadata within the device’s application directory. On both iPadOS and Android, these files may be accessible to anyone with physical access to the device—through tools such as iTunes/Finder (iPad) or the file manager (Android), depending on device settings and platform capabilities.
To protect sensitive information and prevent unintended exposure of critical assets, we strongly recommend that the device not be shared with others if it contains confidential data, proprietary models, or information related to machines and equipment that must remain secure.
For optimal security, ensure that:
-
The device is used only by authorized personnel.
-
Sign out of the AVEVA Connect Account after using the app.
-
Device-level security (passcode, biometric lock, MDM policies) is enabled.
-
Sensitive files are removed when no longer needed.