Important Design Considerations

The capacity of LG webOS devices 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 this platform.

We highly recommend the following:

1. Minimize the file size of graphic media. For example, a 4k Ultra HD video will consume an enormous amount of system RAM, risking serious performance issues.
2. Keep it simple. Because the LG webOS devices are not built to handle large amounts of graphic media and data processing, favor the creation of simple experiences.
3. Test often. Play Mode in Composer does not reproduce the resource limitations of LG webOS. You must run your experience on the LG 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 on Windows offers a superset of capability over Player on LG webOS. This difference will narrow over time but at the moment, not every design option is available for use on tablets.

Please verify that your LG webOS device is compliant with Intuiface Player's minimum device specifications.

Features Never to be Supported

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

• Intuiface Headless CMS
• Websites supporting a same-origin policy. The Web Browser asset requires websites supporting a cross-origin policy.
• 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. See our list of out-of-the-box interface assets for those that will work on LG webOS.

Features Currently Unsupported

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

• Share via Email - Configurable (i.e. using your own SMTP server)
• Helix collection
• Timeline collection
• YouTube asset
• (Microsoft) Deep Zoom asset
• Experiences published to an FTP/FTPS site cannot be downloaded.

Additional Limitations

• Content loaded from Excel Interface Asset will not be displayed if the name of the spreadsheet contains spacing [blank] characters
• Performance
  As mentioned above, an LG webOS device is not built to handle large amounts of graphic media and data processing. The following points reduce the burden on this platform.
  • Prevent asset/collection rotation if acceptable for your design. In particular, use a design that doesn't permit the rotation of multiple items at the same time.
  • Keep 3D models simple and minimize the number of models in a given scene
  • Always use a "View angle" of 0 for the Carousel collection
  • Avoid use of the Book document style
  • Don't use scene transition effects
    • If you must, only the "Cross Fade" effect is available.
• Videos
  • Use the mp4 (H.264) video format in the Video asset. The frame rate should be a multiple of 30 for US displays and a multiple of 25 for displays used around the rest of the world.
  • The number of concurrently played videos depends on the version of webOS. Version 3.0 is limited to playing one video at a time. Version 3.2 can play two videos concurrently. Version 4.0 can play four videos concurrently.
  • Don't nest videos inside a collection
  • Can only use timestamps as a video poster. External images cannot be used as posters.
  • Video poster is displayed regardless of where on the timeline a video is paused.
• Assets and Collections.
  • 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.
  • Minimize capability is not available (including the Initial View State property)
  • Image Assets in an Asset Flow with "Tap item to open" get cropped when manually resized down.
  • Web Browser asset does support website links opened in a new browser window (i.e. _blank)
  • For the Carousel, the "Display back of items" property must be set to True.
  • There is no initial scroll effect for the Asset Flow, Asset Grid, and Carousel collections.
  • For the Map collection
    • No caching of a live session
    • Bing Maps is blank without an API key
  • 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.
• Drawing Tools
  • Snapshot capability is not yet implemented.
• Text Input
  • Caret custom color is not supported
• Triggers and Actions
  • Launch Application action is unavailable.
  • Call URL action is unavailable
• Other
  • Cannot respond to remote actions regardless of the source: neither from a running experience nor a third-party application
  • 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
  • A newer version of Player is not automatically launched after installation