NOTE

• To ensure you haven't accidentally incorporated unsupported features, make sure Play Mode in Composer is set to "Simulate Player on other platforms (iPad/Android/...)". To make this selection in Composer, click the Project menu and choose the option "Simulate Player on other platforms (iPad/Android/...)".
• 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 iPads and Android 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 an 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 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 for Kiosks and Player for Tablets. 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 the iPad and on Android devices.

Features Never to be Supported

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

• (Adobe) Flash Animation asset
• (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 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 the iPad and Android 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 - Android only. Not supported on the iPad
• Scratch Card
• Take snapshot action

Additional Limitations

Android specific limitations:

• If you change the name of the device itself, the new name will only be recognized by Player and the Share & Deploy Console if you quit Player, stop then restart Bluetooth, then restart Player. This is because the device name is taken from the Bluetooth device so the Bluetooth device itself must be made aware of the device name change first. If Bluetooth is already off, just turn it on before restarting Player.

iOS specific limitations:

• Tablet Orientation Interface Asset is not supported
• 3D models are not visible in monitoring via Share and Deploy console

Android and iOS limitations:

• 360° YouTube Videos:
  
  • Tablet orientation changes is not supported. Rendering might be degraded if orientation is changed from landscape to portrait and vice-versa

• 3D Model Asset:

  • On iPad, iOS Version 8.1 or later is required
  • Light rendering differences may be observed on iOS and Android devices
  • Interaction Mode - Orbit using "Keep model in viewport" property set to true, will not be respected.

• API Explorer created Interface Assets
  • Setting a part of the "host" as a parameter will not work when creating a REST Interface Asset using API Explorer

• Bindings:

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

• 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

• DataFeed:
  • Multiple Datafeed and assets will not be ordered in the main collection same as on Windows Player. If multiple data feed and assets are are used on the same collection, they might have different order.

• 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.
  • Drawing Tools actions are not supported yet.

• 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 iOS/Android 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, IntuiPad or a third party application
• HTML asset: 
  
  • You may notice rendering differences between different OS devices
  • On iOS devices, the scrollbar of the asset will not be visible while scrolling HTML scroll-able content
  • iOS 11 only: wrapping text in a div with a fixed size is not rendered properly when the CSS property "letter-spacing" is used without any other warping CSS properties
  • Allow multi-touch gestures property is always True even if disabled. This means that you will always be able to zoom content within the HTML asset.

• Licensing:
  • 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.
  • 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 on either platform.
  • 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 tablet'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)
  • Scroll function is not supported (Android only)
  • Clear Cache action is not supported
  • 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 difference 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 the iPad and Android 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

  • 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.