Building Applications for the Opera TV Store
Please note that parts of this article refers to older Presto-based versions of the Opera TV products (Opera TV SDK 3.x). These versions are still live in a lot of devices that are active in all markets, but most devices shipped since 2015 are based on the newer Blink-based Opera product.
- 18 April 2012: new section for currently known limitations of the Opera TV Store.
- 27 August 2012: explicit note about lack of support for third-party multimedia plugins.
- 5 September 2012: removed the requirement for inclusion of the Opera TV Store API.
- 20 January 2013: added note about modal dialogs and lack of support for
- Building your application
- Requirements specific to Opera TV Store applications
- Submitting to the Opera TV Store
The Opera TV Store is a moderated, hosted catalogue of TV-specific web applications. Developers can submit and share their apps through this portal. It presents end users with a storefront (itself a web-based application) which allows them quick and easy access to the applications.
Applications in the Opera TV Store will be presented as static thumbnail images in a dashboard. Users are able to browse the TV Store catalogue and “install” applications, adding them to their dashboard. Selecting an application launches it in full-screen mode.
The full-screen web applications themselves are not hosted directly on Opera’s servers. The Opera TV Store only acts as a directory, with references to the actual URLs of the applications.
Building your application
Although the Opera Devices SDK is built on the same core rendering engine as our desktop browsers, there are still platform-specific APIs and subtle integration differences that developers need to be aware of. For this reason, it is recommended that developers test their applications on an actual TV running the Opera TV Store and/or with the Opera TV Emulator.
Developing web content for TV brings with it its own challenges – from a difference in user interaction to considerations regarding device capabilities and performance optimisation. For an introduction to some of the necessary adaptations and techniques see our documentation on creating web content for TV and other articles in our TV section.
Requirements specific to Opera TV Store applications
Due to the way in which applications will be integrated into, and launched from, the Opera TV Store, developers need to be aware of the following additional requirements:
All TV Store applications have to support 1280×720 resolution. Other common TV resolutions (1920×1080, 960×540) are currently not supported. Although the TV Store browser itself supports regular scrolling, applications should be designed not to require scrolling, and if needed should provide their own custom mechanisms for displaying long lists of items or content.
Navigation and functional keys
The Opera TV Store is designed to use the standard four-way directional keys on a remote control for spatial navigation. Authors should test that their applications work correctly using the default spatial navigation built into the Opera TV Store browser. Authors may also choose to handle the navigation of their application themselves by intercepting key presses from the remote control. As the exact key codes for remote control functional keys varies between different devices, the Opera TV Store browser provides built-in constants (tailored to the device currently running the TV Store). See the article on Functional key handling in Opera TV Store applications for further details.
Multimedia plugins / Flash
The Opera TV Store does not provide support for any third-party plugins, such as Adobe Flash. Any multimedia features and functionality needed by an application must be implemented using HTML5 technologies such as
<canvas> or the native support for
Once an application is launched from the dashboard, it is effectively opened full screen in a new window. The Opera TV Store browser (based on the Opera Devices SDK, responsible for rendering the applications and the TV Store itself) does not present any standard interface elements to the user – it runs as a completely “chromeless” browser, with no address bar or back button. Users will be able to close the application and return to their dashboard via the remote control’s EXIT and/or RETURN key. Developers should nonetheless provide an explicit option or button in their UI to close the application, with a simple call to the
Limitations of current implementations
There are known limitations in some of the current devices that are shipping with the Opera TV Store, generally due to the way certain features have been integrated on the devices by the manufacturers and which version of the TV Store software has been used.
- Missing CORS (Cross-Origin Resource Sharing) support: if your application relies on cross-origin resources (particularly via
XMLHttpRequest), you will need to implement some form of proxy on your application’s origin domain to relay the resources from other domains.
- Due to the integration with external media playback frameworks on certain devices, it may not be possible to guarantee simultaneous playback of more than a single
Submitting to the Opera TV Store
Once your application is ready, it can be submitted to the Opera TV Store. Log in to the Opera TV Store – Submission portal and follow the steps required in the submission dialog.
This article summarises the most important guidelines that applications need to follow for inclusion in the Opera TV Store. Further restrictions and requirements are listed in the acceptance criteria of the Opera TV Store application publishing guidelines. Please ensure that your application fulfills those criteria – as well as the best practices and suggestions laid out in our developer articles – before submitting your application.