Video Player Engineering

Unified video player libraries, DRM implementation, and adaptive streaming across Shaka, Video.js, Radiant, Media3, and native platform players. Write once, play everywhere.

Discipline
  • video
  • drm
  • streaming
  • framework
Tenure
2019 - present

The problem

Every streaming platform needs a video player. Every platform ships a different one. Samsung uses AV Player. LG has its own native player. On the web you pick between Video.js, Shaka, Radiant, or raw HTML5. Android has Media3. Writing player code from scratch for each platform, for each project, was eating weeks.

What we built

A unified Player Framework. One API that wraps five different players behind a consistent interface. Write your playback logic once, it works everywhere.

Players we support

DRM

Premium content needs Widevine DRM. We handle license servers, key rotation, and all the platform-specific edge cases that only show up on actual hardware.

Adaptive streaming

HLS and DASH with quality switching based on network conditions. Smooth playback even on constrained devices.

Analytics

We instrument every player with QoE metrics: startup time, rebuffer ratio, dropped frames, seek latency, session lifecycle. Everything feeds into dashboards so teams can see what real users experience.

Impact

This framework is not a proof of concept. It runs in production across major telecom operators, pay-TV providers, and national broadcasters in Turkey and the Middle East. Every player integration we have shipped since 2019 has gone through it.

Tech

Shaka Player · Video.js · Radiant Player · Media3/ExoPlayer · HTML5 Video · Samsung AV Player · LG webOS Player · Widevine DRM · HLS · DASH · Ktor · Grafana


Dealing with player headaches across platforms? Get in touch.