We have video player extracted in a separate npm package, as both TV web app and .com web app use it.
It abstracts all player logic, and uses 2 main open source players, based on a platform and content where it's used.
Shaka player is our main player, for standard DRM content.
Hls.js is a player we use for live streams, continuous TV streams.
This covers most of the cases, but there are edge cases where we use other players.
Like some of the older models of Tizen and WebOS TVs, where we load their native platform players for DRM content.
And on modern iOS Safari browsers, we load their native player, as it fully supports HLS content, so there's no need for a custom built player like shaka or hls.js.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Helpful article, can i ask what video player did you use?
We have video player extracted in a separate npm package, as both TV web app and .com web app use it.
It abstracts all player logic, and uses 2 main open source players, based on a platform and content where it's used.
Shaka player is our main player, for standard DRM content.
Hls.js is a player we use for live streams, continuous TV streams.
This covers most of the cases, but there are edge cases where we use other players.
Like some of the older models of Tizen and WebOS TVs, where we load their native platform players for DRM content.
And on modern iOS Safari browsers, we load their native player, as it fully supports HLS content, so there's no need for a custom built player like shaka or hls.js.