Design and playback considerations when using Player for Samsung SSP


    The capacity of the Samsung SSP's onboard CPU to 1) manage a large number of graphics in a single IntuiFace scene and 2) keep in memory large graphic media files, 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 the SSP.

    We highly recommend the following:

    1. Keep it simple. Because the Samsung SSP is not built to handle large amounts of graphic media and data processing, favor the creation of simple experiences.
    2. Test often. Play Mode in Composer does not reproduce the resource limitations of the SSP. You must run your experience on the SSP in order to assess its true performance quality.
    3. Review the recommendations below.
    4. Consider use of an external Windows PC vs. use of the onboard CPU. Performance will benefit significantly. Of course, cost will go up as well.

    Please check that your SSSP is compliant with IntuiFace Player in this section.

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