Our support site has moved to https://support.intuiface.com

Player for Tablets and Player for Kiosks - Limitations

Table of Contents


    • To ensure you haven't accidentally incorporated unsupported features, make sure Play Mode in Composer is set to use 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 iPad devices, see this page.
    • For a list of supported Android OS versions, see this page.

    Important Design Considerations

    The capacity of the iPad and Android tablets 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 a tablet.

    We highly recommend the following:

    1. Minimize the file size of graphic media. For example, a 4k Ultra HD video on the iPad 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 iPad or on an Android tablet 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 for iPad and Android. This difference will narrow over time but at the moment, not every design option is available for use on tablets.
    5. Test your webpage in the native tablet browser to make sure it is rendered properly. Some websites are rendered differently when opened on tablet devices and this is how those sites will appear in Player for iPad and Player for Android.

    For a detailed list of design recommendations, see this article.

    Features Never to be Supported

    Certain IntuiFace capabilities available in Player for Windows will never be available in Player on iPad or Android because the underlying technology is not supported by the tablet operating system:

    • (Adobe) Flash Animation asset
    • (Microsoft) Deep Zoom asset
    • Websites supporting a same origin policy. The Web Browser asset requires websites supporting a cross origin policy. If you attempt to load a website with a same origin policy, the Web Browser asset will display an error message stating the connection was "refused" due to "X-Frame-Options".
    • 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 the iPad and Android, see this page
    • iOS constraint: Only one video or audio file can be played at a time.
    • iOS constraint: Volume for videos and audio can only be controlled using the iPad's physical volume buttons. In app controls won't work.

    Features Currently Unsupported

    The following capabilities are not yet part of IntuiFace Player on iPad or Android but may be added in future releases:

    Additional Limitations

    • HTML assets nested within collections will not fire Triggers and Actions.
    • Every Player login initiates a new license request; a license is neither released nor remembered by Player after logging out. As a result, more than one license can be checked out for the same tablet. To release a tablet license back into the license pool, follow the directions here.
    • 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 set on 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
    • Video and Audio Assets
      • Use mp4 format for video on the iPad;
      • Use mp4 or webm for video on Android. The Microsoft wmv format is not supported on either platform.
      • Only one video/audio can be played at a time.
      • Can only use time stamps 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 tablet's physical volume buttons.
      • “Title” property of the Video, Audio and Document assets is not supported.
    • 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"
    • Web Browser asset

      • No support for website links opened in a new browser window (i.e. _blank)
      • No support for "link is clicked" trigger
      • Scroll function is not supported (Player for Android only)
      • Clear Cache action is not supported
    • 3D Model Asset

      • On iPad, iOS Version 8.1 or later is required
      • Light rendering differences may be observed on iOS and Android devices
    • Text Input Asset

      • Keyboard customization and specific properties are not supported as the native OS keyboard is used on the iPad and Android devices.
      • Keyboard's "Standard + Numpad" layout is not supporter on Players for Tablets and Kiosks devices, the "standard" layout or the native keyboard will be shown instead.
    • 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
    • Drawing Tools

      • Snapshot capability is not yet implemented.
    • Visual Effects

      • The two Shape assets - Rectangle and Eclipse - do not support use of the Blur, Grayscale, Sepia, Hue rotation and Brightness effects
    • General

      • Concurent animations performed on the same asset are not managed.
      • 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 remote actions regardless of the source: neither from a running experience, IntuiPad or a third party application
    • 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 iOS/Android standard fonts.