In this video, Moodle HQ Development Process Manager Cameron Ball gives us reasons why they decided to go with Video.js as the Moodle 3.2 default handler of video and audio files.
The customizability and personalization of Moodle 3.2 knows no virtual limits, and the choice of a player could not be any different. But Video.js is flexible enough to cater to most customer needs, not to mention it’s Open Source. Many Moodle sites, particularly those that feature third-party components, still rely on Adobe Flash. But the web presence of Flash is dwindling, ever since Steve Jobs decided not to support the technology on Apple’s iPhones.
The coming of HTML5 would be another fatal, if not yet deadly, blow to Flash. The Edge and Chrome browsers are suggesting developers to begin decommissioning it. Even Adobe itself is preparing for a Flash-less future, by allowing Moodle favorite plugin Adobe Connect to work without Flash since 2016 version 9.5.2.
As Ball explains, Video.js is highly compatible with both modern browsers and media file extensions, while ensuring a consistent layout and simple set up by Moodle teachers and admins. Even Internet Explorer 9 supports it.
Students on Mobile, be it through the app or the mobile browser, will have no problem watching video on the go. It is also trivial to add captions, and subtitles in as many languages as your heart deems enough to be content, making for “industry-leading accessibility and usability for video and audio“, Ball claims.
For sites who are not quite there on letting go of Flash, or other player, they can be added thanks to Video.js pluggable support. As default, Video.js can also be overridden on the admin settings panel.
Adding a video is just a matter of clicking the media icon whenever a text editor is available to create content or to edit a page.