Upgrading Apps for New Platform

If you already have webOS TV apps published, there are a few changes you need to consider to make your app support new webOS TV platform versions. Here are a few points we would like to let you know for a quick start.


  • Magic remote’s exterior design is changed. See Remote Control to find out more information.  

  • In addition to Enyo, Enact is newly supported as the JavaScript framework. For more information about Enact, see Enyo/Enact Guides. Enyo is not supported by webOS TV that will be released in 2019 (version will be 4.5). However, if Enyo libraries and resources are packaged along with your app, it will be compatible for execution.

  • Supported Media Source Extensions (MSE) and Encrypted Media Extensions (EME) versions are provided in Supported Media and DRM Formats.

  • UX checklist is updated.

  • webOSTV.js, an alternative library of webOS.js for accessing to TV-specific features, is available to handle TV-specific features.

  • Unnecessary properties of appinfo.json are removed.


  • The web engine of LG Browser in webOS TV 3.x is upgraded to Blink. This resulted in a few changes including the value change of the userAgent string.  

  • There are some changes in Standard Web API

    • webOS TV 3.x supports more properties and methods of Video/Audio Element, IndexedDB, and Canvas. 

    • Google’s WebM media format is now supported. To learn more, refer to Supported Media and DRM Formats

  • USB App Test service is no longer available on real TVs. Developer Mode app has been introduced to provide a more comfortable testing environment. Read App Testing for more details.  

  • A Luna Service API, Device Unique ID, has been added. It generates the device’s unique ID for apps and their services. To find out more about this API and its method, see Device Unique ID

  • In addition to Enyo 2.3 and 2.5, Enyo 2.6 is newly supported. 

    • In Enyo 2.6, enyoVersion, onDeviceSource properties are no longer used. Use Enyo 2.3 or 2.5 for these properties.

    • disableBackHistoryAPI has been added as an App Metadata (appinfo.json) property. This property sets whether your app can receive the back key event when the remote’s back button is pressed. For more information, see App Metadata (appinfo.json).