There are several ways to add media to a web page. Previously you learned how to
use the standard
<video> tag. In this article you will learn about a few of the
media frameworks (or libraries) available that you can use to extend or replace
the behavior of the default HTML5 video player.
Media frameworks come in both the proprietary and open-source variety, and at their core are a set of APIs that support audio and/or video playback for various container formats and transmission protocols. A good framework has a modular architecture and provides clear and detailed documentation. Ideally it should also be relatively easy to set up and use. You might be asking yourself, "If the HTML5 video player provides most features already then why would I use a framework or library?" That's a great question, let's dig in.
Benefits of using a framework
In most situations that are beyond the needs of a basic web page, you are going to want to use a media framework to serve your content. Unless you are prepared to develop and maintain a rich feature set like offline playback, streaming, analytics, picture-in-picture, preview thumbnails, embedding, and monetization such as fill rate optimization, Ad scheduling, or header bidding to name a few then you should probably offload that complexity to an existing solution.
This is where media frameworks come in. They provide you with a set of features, and conditions in which you can use those features, and then you have to decide which framework is right for your project. In the next article we will discuss how we built a PWA with offline streaming that implements several complex features. Spoiler alert, it was a lot of work and is still far from being a production ready solution. Save yourself the headache and use a framework.
With Shaka you will need to host and encode your media files yourself. Creating a media server is not overly complex, however encoding/transcoding media can be time-consuming and complicated. You will likely want to offload this part to a service such as Zencoder, Amazon Elastic Encoder, or Google Transcoder API to automate repetitive tasks and speed the process up.
The great thing about the Shaka Player is there is also a really fantastic tool and media packaging SDK for DASH and HLS packaging and encryption called Shaka Packager. It can prepare and package media content for online streaming, which you learned about earlier in Media conversion and Media encryption.
If you are looking for an option that provides hosting and encoding/transcoding services then you might look into JW Player, but keep in mind that JW Player is proprietary software. Meaning, you don't have much control over the platform or roadmap. There is a basic free version where videos are displayed with a watermark, and a commercial version.
JW Player supports streaming with MPEG-DASH (paid version only), Digital rights management (DRM) (with Vualto), interactive advertisement, customization of the interface, and embeds. There is a well documented API and SDK. However, if you are just looking for a quick and free way to host your media then embedding YouTube videos are typically going to be your best free option.
According to their website, Video.js is built from the ground up for an HTML5 world. It supports HTML5 video and modern streaming formats such as DASH and HLS, as well as YouTube, and Vimeo. It supports video playback on desktop and mobile devices and looks good everywhere with CSS-based skins.
There are a few ways to use Video.js, but the easiest is to use the free CDN version provided by Fastly. You can learn more on how to get the player set up on the getting started page. Video.js is a very powerful video player, and much like Shaka Player you will also need to host and encode your video. However, one difference is in the plugin system where you can do things like play YouTube videos in the Video.js player, which can also be customized.
There are lots of different frameworks and libraries available, this article only scratches the surface on what is out there. When choosing a framework you should consider what features you need for the project and how you plan to host and encode or transcode your media. Do you need pre-roll Ads or other monetization strategies? Will your media be available offline? How big or small is your budget? Or any other number of considerations. Do your research and ask people in your network for suggestions. There are dozens of other great options and before you make any choices take some time to pick one that will be right for your team and avoid creating unnecessary technical debt or complexity to maintain during the project lifecycle.
Next, you will learn about the PWA with offline streaming we built to demonstrate how to approach and tackle the main challenges that come with rolling your own solution using just the HTML5 video object without a framework to handle the heavy lifting.