Getting started with Smart TV development
Flowplayer Native, the Flowplayer web player, runs on web-based Smart TV platforms such as Tizen and webOS much as it does in a regular web browser, with a few platform-specific pitfalls to be aware of.
Table of contents
Running Flowplayer Native on Smart TVs
The approach to get Flowplayer running on web-based Smart TV environments (like Tizen or webOS) is similar across all platforms.
The normal Flowplayer web player works similarly to how it works in a normal web browser, but there are some gotchas to be aware of.
Common pitfalls
Remote control support
In order to make the player usable with a TV remote control, you need to include a Smart TV plugin. Which plugin to choose depends on the underlying platform.
We offer plugins currently for Tizen and webOS.
Media URLs and media types
Most of the web-based Smart TV platforms are running a Chromium-based browser as the view layer.
The application is served from the filesystem directly with file:/// protocol. This means that you can't use
protocol-relative media URLs (//cdn.example.com/myfile.mp4). You need to always include the full absolute media URL with protocol: https://cdn.example.com/myfile.mp4.
The Chromium-based browser most likely only supports MP4 files out of the box. In order to run HLS or MPEG-DASH content you need to include the matching Flowplayer playback plugin when you initialize the player. See the respective plugin documentation to see how to include them: HLS, MPEG-DASH.