Important Design Considerations

The capacity of the Amazon Signage Stick 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 sluggishly on other platforms.

We highly recommend the following:

1. Minimize the file size of graphic media. For example, a 4 K Ultra HD video on a Signage Stick will consume an enormous amount of system RAM, risking serious performance issues, while adding no aesthetic value to such a physically small screen.
2. Endorse modularity. Choose a small number of images on multiple scenes rather than a large number of images on a small number of scenes.
3. Test on the device early and often. Although Composer's Play Mode enables testing, the underlying technology still runs on a Windows PC. You must run your experience on the target device to assess its actual performance.
4. Review the rest of this page to ensure you are familiar with all limitations.
5. Test your webpage in the native device browser to ensure it renders properly. Some websites render differently across devices, so only the native device browser will show you how they will appear in Player running on the Signage Stick.

Features Never to be Supported

Certain Intuiface capabilities available on other platforms will never be available when running Player on Android-based devices because the operating system does not support the underlying technology:

• Any JavaScript-based Interface Asset. All out-of-the-box interface assets are being rewritten using TypeScript. Any customer-created interface assets must be rebuilt using Intuiface's TypeScript CDK.
• 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.

Amazon Signage Stick-Specific Limitations

• Signage Sticks do not support touch-based interaction.
• Without a USB port, Signage Stick cannot be used with any USB-based extensions, such as a Webcam or Nexmosphere.
• Low performance for video decoding. If possible, use streaming media instead.
• Web Browser
  • "Disable Scroll" Web Browser property is not supported
  • "Website fails to load" triggers will not be raised
• Use of "Call URL" for http targets is not supported
• Interface Assets using the 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
• 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 will be used
  • Keyboards "Numpad" and "Standard + Numpad" layout are not supported. The native keyboard will be shown instead.
• Text Asset
  • Text-overflow behavior is not supported
• Only the internal storage can be used to store experiences. Storage expansion options - such as an SD card - are not supported.
• When updating an experience, the device's internal storage must have at least as much free space as the updated experience requires. (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.