
Save your time. Save your tokens. Just use Video.js.
Video and video players are really hard, and I wish more people knew the extent of it. One common mistake that will happen until the end of time, especially with AI now, is devs trying to build players with application UI component libraries. I've spent years building player frameworks. If it were truly that simple, I wouldn't have spent a second on it. A player is an app inside your app. The state isn't owned by your app, not fully, it's owned by the media. It's async. It can leave the page entirely (mount/unmount), and specific state resets when the provider or source changes. Capabilities exist or don't depending on the browser, device, media, and source. Managing all of this state alone is _very_ hard. There are also specific accessibility requirements for each component, and UI/UX expectations around a player. A time slider is not a standard slider. The value moves on its own. Seeking is async, and browsers report stale times mid-seek, so the thumb snaps back after you let go. A lot of bugs will surface on slow networks. Duration can be NaN (no metadata) or Infinity (live). It needs buffered progress, chapters and hover previews. Screen readers need time phrases like "1 minute 23 seconds of 10 minutes", not "83". Time updates are choppy and inconsistent, so you need your own rAF loop. Media buttons aren't just buttons. Fullscreen on iPhone takes only the video and drops your controls. Every button usually includes capability checks and state transitions. Certain UI components need special treatment in fullscreen and picture-in-picture. Playback state changes need to be announced to screen readers. Ensuring the player functions consistently across different browsers adds another layer of complexity. Browsers may have varying levels of support or distinct APIs for certain media features. And that's just some of it with an MP4. Add streaming (HLS/DASH), live, quality, audio tracks, captions, remote playback (AirPlay, Google Cast) and DRM, and it just keeps getting more complicated. I could go on forever. None of this is generic. We do a ton of work over on @videojs so you don't have to think about any of it. We want it on the surface to feel like you're working with just another UI library, and for the player to feel like part of your app. But it isn't one underneath.











