- To ensure you haven't accidentally incorporated unsupported features, make sure Play Mode in Composer is set to "Simulate Player on other platforms". To make this selection in Composer, click the Project menu and choose the option "Simulate Player on other platforms".
- For a list of supported Android devices, see this page.
Important Design Considerations
The capacity of Android based devices to 1) manage a large number of graphics in a single Intuiface scene and 2) keep in memory large graphic media files and animation is equivalent to that of a modestly powered Windows PC. As a result, an Intuiface experience that performs well on a Windows PC might act sluggish on other platforms.
We highly recommend the following:
- Minimize the file size of graphic media. For example, a 4k Ultra HD video on an Android device will consume an enormous amount of system RAM, risking serious performance issues, while contributing no aesthetic value on such a physically small screen.
- Endorse modularity. Choose a small number of images on multiple scenes rather than a large number of images on a small number of scenes.
- Test on the tablet often. Even though Composer's Play Mode includes an option for simulating tablets, it does not reproduce a tablet environment. You must run your experience on the target device in order to assess its true performance quality.
- Review the rest of this page to be sure you are acquainted with all limitations. Player for Windows offers a superset of capability over Player running on Android based devices. This difference will narrow over time but at the moment, not every design option is available for use on other platforms.
- Test your webpage in the native device browser to make sure it is rendered properly. Some websites are rendered differently from one device to another and this is how those sites will appear in Player running on Android devices.
Features Never to be Supported
Certain Intuiface capabilities available in Player on Windows will never be available when running Player on Android based devices because the operating system does not support the underlying technology:
- (Microsoft) Deep Zoom asset
- Any Interface Asset using a .NET DLL. Over time, all out-of-the-box interface assets will be built using REST or TypeScript, both of which are cross-platform technologies.
- Websites that require same-origin policy. The Web Browser Asset can only display websites that permit cross-origin resource sharing - i.e. that don't require a same-origin policy. If you attempt to load a website requiring a same-origin policy, the Web Browser asset will display an error message stating the connection was "refused" due to "X-Frame-Options". Most public websites (such as Google, Facebook, Instagram, Twitter, YouTube, ...) require the same-origin policy and cannot be displayed in Player on Android. Sites like these may be accessed using embeddable code placed within the HTML Frame Asset instead.
Features Currently Unsupported
- Please refer to the General Limitations article for a list of known limitations.
Android Specific Limitations
- Web Browser
- "Disable Scroll" Web Browser property is not supported
- "Website fails to load" triggers will not be raised
- Webcam Asset
- Android-based devices do not support multiple Webcam Assets in the same scene.
- Share and Deploy console - Experience live Snapshots
- Call URL to http targets are not supported
- Interface Assets using http protocol will not be resolved. Your Interface Asset must use https instead.
- Remote Actions are not supported.
- Video and Audio Assets
- Can only use timestamps to assign a poster to a video. External images cannot be used as posters.
- “Title” property for the Video and Audio assets is not supported.
- Video loaded from distant sources or from a DataFeed might not display a poster frame when running on Android devices
- In certain cases Video and Audio content might not be loaded. As a workaround, the "Play" action (using Triggers and Actions) can be used on the video to force the loading.
- Text Input Asset
- Keyboard customization and specific properties are not supported as the native OS keyboard is used on Android devices.
- Keyboards "Numpad" and "Standard + Numpad" layout are not supported. The native keyboard will be shown instead.
- Only the internal storage can be used to store experiences. Storage expansion options - such as an SD card - are not supported.
- GBoard Virtual keyboard is not supported for Text Input asset, if used, it may have unwanted results
- When updating an experience, the device's internal storage must have free space at least equal to the size of the updated experience. (This is in addition to the space already used by the original version of the experience already on the device.) The downloaded experience will be removed but is temporarily required to facilitate the update.
- Text Input Asset
- Keyboard customization and specific properties are not supported as the native OS keyboard is used on the iPad and Android devices.
- Keyboards "Numpad" and "Standard + Numpad" layout are not supported. The "Standard" layout of the native keyboard will be shown instead
- Share and Deploy Console
- Snapshot (live tracking in Share and Deploy Console) is not supported