NOTE

• To ensure you haven't accidentally incorporated unsupported features, make sure Play Mode in Composer is set to "Player for Tablets and Kiosks". To make this selection in Composer, simply click the Project menu and choose the option "Use Player for Tablets/Kiosk".
• For a list of supported Chrome devices, see this page.

Important Design Considerations

The capacity of Chrome 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:

1. Minimize the file size of graphic media. For example, a 4k Ultra HD video on a Chrome device will consume an enormous amount of system RAM, risking serious performance issues, while contributing no aesthetic value on 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 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.
4. 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 on Chrome. This difference will narrow over time but at the moment, not every design option is available for use on other platforms.
5. 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 on Chrome.

Features Never to be Supported

Certain Intuiface capabilities available in Player on Windows will never be available in Player on Chrome because the underlying technology is not supported by the associated operating system:

• Intuiface Headless CMS: Support for H-CMS on Chrome will be introduced with Player Next Gen.
• (Microsoft) Deep Zoom asset
• Websites that require a 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 Chrome devices.  Sites like these may be accessed through the use of embeddable code placed within the HTML Frame Asset instead.
• Any Interface Asset using a .NET DLL. Over time, all out-of-the-box interface assets will be built using REST or JavaScript, both of which are cross-platform technologies. For a list of which out-of-the-box interfaces are available on Chrome devices, see this page.

Features Currently Unsupported

The following capabilities are not yet part of Intuiface Player on Chrome but may be added in future releases:

• Share via Email - Configurable (i.e. using your own SMTP server)
• Share via filesystem
• Share via USB
• Helix collection
• Timeline collection
• Circular panel
• On Screen Gestures - only supports Swipe Up/Down, Swipe Left/Right.
• Webcam Asset
• YouTube Asset
• Scratch Card
• Take snapshot action

Additional Limitations

• 3D Model Asset:

  • Light rendering differences may be observed on iOS and Android devices
  • Interaction Mode - "Keep model in viewport" property, even when set to true, will be ignored by orbit

• Bindings:

  • Binding the height of an asset will apply a scale resulting in a visually deformed asset

• Share and Deploy Console:

  • ChromeOS devices will not expose particular device names in the management console. You should use unique tags in the console management on each device to identify them.

• Collections:

  • There is no initial scroll effect for the Asset Flow, Asset Grid, and Carousel collections.
  • Only Scale is managed for items in a Group
  • Asset Flow and Asset Grid collections do not manage "justify". When the collection contains fewer items than can fit in a single view - e.g. 3 items in the collection while 5 could be displayed - then items are left-justified.
  • For the Map collection
    • No caching of a live session
    • Bing Maps is blank without an API key

• Design Accelerators:

  • Item Picker

• Document asset:
  • Book style is not rendered the same as on Windows devices. The container for a book document will be white and not transparent.
  • For the Book style, the following properties are not yet recognized
    • "Show page numbers"
    • "Reading direction" (it is always Left to Right)
    • "DPI"
    • "Show scroll indicator"
  • For the Book style, the following actions are not yet recognized
    • "First page"
    • "Last page"

• Drawing Tools:

  • Snapshot capability is not yet implemented.

• Excel Interface Asset:

  • Unable to read values from cells referencing another sheet that has a spacing character in its name

• Fonts:

  • Some Windows fonts are rendered differently than they appear on Windows PCs. The following contains the known list of fonts with rendering differences but there may be others.
    • Bookshelf Symbol 7
    • Calibri
    • Marlett
    • MS Outlook
    • MS Reference Specialty
    • MT Extra
    • Times New Roman
    • Webdings
    • Wingdings
    • Wingdings 2
    • Wingdings 3
  • In some cases, certain Bold and Italic fonts may be replaced by Chrome standard fonts.

• Functionality:

  • Concurrent animation performed on the same asset is not supported. For example, you can't rotate and resize an image at the same time.
  • Launch Application action is unavailable. Call URL action can be used instead.
  • Minimize capability is not available (including the Initial View State property)
  • Preview Mode requires that each individual media file used in an experience be no larger than 100 MB.
  • Cannot respond to local network triggers or remote actions regardless of the source: neither from a running experience, peripheral, or a third-party application

• HTML asset:
  
  • You may notice rendering differences between different OS versions

• Image asset
  • WebP images from an Excel Interface asset source are not supported

• Scenes:
  • Scene transition effects may greatly decrease the performance of your experience and could even lead to a crash. Limit their use.
  • Triggers with Actions defined for a different scene are not supported.
  • Videos cannot be used for either the experience or scene Background property. Use an experience layer instead.
  • The following scene transition effects are not available:
    • Circular
    • Wipe
    • Black Fade

• Share via E-mail Hosted Interface Asset:

  • Offline stored e-mails will be destroyed if a Player log-out action is performed. This means, the e-mails will not be sent when the device comes back online, even if you log back in using the same account.
  • Sending E-mails with a distant attachment is not supported. The attachment resource must be locally present on the device. Use Interface Asset - Shopping List instead.

• Video and Audio Assets
  • For Video use MP4 format with H.264 codec. Mp4v-20 codec is no longer supported.
  • Microsoft WMV format is not supported
  • Can only use timestamps to assign a poster to a video. External images cannot be used as posters.
  • Video and Audio asset volume can only be controlled using the device's physical volume buttons.
  • “Title” property of the Video, Audio, and Document assets is not supported.

• Web Browser asset

  • No support for website links opened in a new browser window (i.e. _blank)
  • No support for "Link is clicked" trigger
  • Clear Cache action is not supported
  • "Has Been inactive" trigger will fire when manipulating the Web Browser
  • Very Complex Web Pages may crash the player, in this case reducing the browser's asset resolution property may help
  • Scrolling of web pages will not work if the page changes size dynamically without reloading.

• Text Asset

  • Avoid using centered text that includes spacing characters. Centered text that has spacing characters. For example "   text" will include the spacing when the text is centered. As a result, rendering differences may be observed between platforms when centering text containing spacing.

• Text Input Asset

  • Keyboard customization and specific properties are not supported as the native OS keyboard is used on Chrome devices.
  • Keyboard's "Standard + Numpad" layout is not supported; the "standard" layout or the native keyboard will be shown instead.
  • Avoid using centered text that includes spacing characters 

• Triggers and Actions

  • Actions targeting assets on a different scene will not be executed
  • Returned Trigger coordinates will always be asset-based. In other words, the value of the coordinates will be relative to the asset itself and not the scene.