Nice work! As someone that uses https://github.com/sampotts/plyr in one of my projects (and react-plyr), what are the main differences between the two players & designs?
Plyr is really good and has an impressive UI and accessibility. But there is no way extend the player with new complex functionality or a tighter integration with Shaka/hls.js/other ad providers/...
I think Plyr can be seen as a better and unified UI on top of a <video> element, while this is an extensible player 'framework'.
I can't speak for plyr as I am not familiar with their project. What I like about indigo is the way modules are structured, the initial file (indigo-player.js) loads the needed code in order to provide playback, it's basically a mono repo. I've spent a fair amount of time on state management too, meaning you have a well defined & standardized API no matter whether you play DASH/HLS or use FreeWheel / Google IMA ads.
Comments
Nice work! As someone that uses https://github.com/sampotts/plyr in one of my projects (and react-plyr), what are the main differences between the two players & designs?
Plyr is really good and has an impressive UI and accessibility. But there is no way extend the player with new complex functionality or a tighter integration with Shaka/hls.js/other ad providers/...
I think Plyr can be seen as a better and unified UI on top of a <video> element, while this is an extensible player 'framework'.
Excellent answer - I get it now. Thank you!
I can't speak for plyr as I am not familiar with their project. What I like about indigo is the way modules are structured, the initial file (indigo-player.js) loads the needed code in order to provide playback, it's basically a mono repo. I've spent a fair amount of time on state management too, meaning you have a well defined & standardized API no matter whether you play DASH/HLS or use FreeWheel / Google IMA ads.
Edit: the state interface can be found here: https://github.com/matvp91/indigo-player/blob/master/src/ext...