Design and playback considerations when using Player on iPad and Android

    Design Recommendations

    • Use the exact pixel resolution of the target display: The New Project panel contains Display Size presets corresponding to the pixel dimensions of various tablets and displays. Choose the exact match whenever possible as this helps the image optimization process used by IntuiFace to minimize the memory consumed by images.
    • Minimize the size of content: Be proactive and limit content to the size of the target display. For images in particular, keep them below 2 to 3MB - a dimension of about 1920x1080. By downsizing content proactively - e.g. reducing the resolution of a video that will never be more than 500x300 in size - you reduce the amount of system resources consumed. This can be a big resource saver. (One shortcut: use jpg instead of png for images as the former uses fewer system resources at the same resolution.)
    • Hide everything the user is not meant to see: Everything visible - even if just slid off-screen - consumes device resources. To prevent this consumption, deselect the "Visible" property of every unseen asset, collection and control. When the item is meant to be revealed, use triggers and actions to unhide the asset.
    • Minimize the use of binding to access image content: If image content is accessed via binding to external sources, those images can't be proactively optimized in size to minimize the system memory they consume.
    • Avoid single scene experiences with lots of visible content: The issue here is the amount of system memory required to show everything in a single scene. Tablets have limited memory so designs should consider minimizing memory use to optimize performance. Note that hidden content doesn't consume system resources. The issue is visible content only.
    • Enable virtualization if you're display a large number of images in collections: The virtualization setting - found in the Players's Settings panel - is an attempt to compensate for the limit memory provided by tablets. The trade-off is a reduction in performance as images are swapped in and out of memory.
    • Reduce PDF quality" This is another example of trying to minimize the memory burden of your experience on the tablet. You can adjust this setting for the Document asset using the Appearance property named DPI.s
    • Be careful about referencing PDFs in Excel spreadsheets When opening a PDF document referenced in an Excel spreadsheet, Composer/Player will first have to import the PDF before it can be displayed, resulting in a (potentially significant) delay. When possible, add PDFs to your experience at design time so the import process is completed before deployment.
    • Do not use the Web Browser asset if it can be avoided: If you must use it, set it to a static container and ensure the webpages displayed only contain animation intended for mobile devices (e.g. less than 60 FPS)
    • If possible in your designs, enable "Maximize videos to fullscreen": In the Player settings panel, selecting this option will increase the amount of system resources dedicated to video playback. Specifically, maximized videos will use the native iPad video player - QuickTime - and not the player used by IntuiFace.
    • Unhide assets before animating them: Use of animation actions - like Animated Move To work more effectively if the item being animated is unhidden.
    • Reduce rendering detail of audio: Related to the prior point. Limit audio bitrate to 1500 kB/s or less. (Same goes for videos.)
    • Use visual effects sensibly: IntuiFace includes some very cool visual effects like blur and grayscale. These effects are amazing but can require a lot of processing power. Feel free to use them but do so judiciously - e.g. apply one at a time and only as much as necessary. And always test your work.

    Playing Experiences Created Using Composer Free

    Only a free Player for iPad or Android can be used to play Composer Free experiences. When Player is licensed, it is unable to open and play Free Edition experiences.

    Preventing use of iPad Home button when running Player

    Enable Guided Access mode to prevent use of the Home button, useful if you need to enable kiosk mode on an iPad device. For more information, visit this page. Ensure you record the Guided Access password because only a factory reset can close Guided Access if the password is forgotten.

    Preventing use of Android buttons and menus when running Player

    Enable screen pinning as described in this article to prevent the use of all Android buttons and menus, useful if you need to enable kiosk mode on an Android device. Screen pinning is a feature introduced by Android Lollipop.

    Mirroring the iPad on a second display

    As with most other iPad apps, the iPad Player can be used with AirPlay to mirror the iPad display on a second screen. Of course, even if that second screen is touch-enabled, touch events will not be registered. Only the iPad can be used to capture touch.

    You can also directly attach your iPad to a second display via a Lightning-to-HDMI adapter.