Skip to content
Workshop
← All work
Media, online streamingJanuary–July 2025Contract work, remote

Stable playback on TV apps through live 4K streams of over two hours

I worked on the TV apps of a live sports streaming platform whose peak traffic exceeded 500,000 concurrent viewers. Playback stayed stable even in long live 4K streams of over two hours.

Endeavor Streaming (part of Deltatre since September 2025) · official job title: Senior Cross-Platform Engineer

System diagram

Live sport streaming: one codebase, three interfacesSystem diagram. Endeavor Streaming's live sports broadcasts reach mobile, web and TV interfaces built in one Nx codebase. The TV versions run on tvOS and Android TV. For complex animations I trialled the new architecture (Fabric/JSI) in the link between JavaScript and native code. Video uses the device's built-in player, and I worked around its limits.Endeavor Streaming platformlive sport, 15+ platformslive broadcastOne Nx codebaseMobileWebTVtvOS · Android TVRemote-control navigationJavaScriptinterfaceNativepartFabric / JSI (pilot)~30% less UI-threadblocking in theanimations measuredThe device's built-in video playerlong 4K sessions: working around its limits

According to Deltatre's July 2025 announcement, the platform I worked on powered services including UFC Fight Pass, WNBA League Pass and NWSL.

Deltatre announcement, July 2025 ↗ — This public figure is about the company or product, not my personal result.

The situation

Endeavor Streaming streams live sport on more than fifteen platforms, with customers that include UFC Fight Pass, WNBA League Pass and NWSL. On Apple TV and Android TV, people select and open items with a remote control, not by touch.

What made it hard?

Playback had to stay stable on the TV apps during live 4K streams of over two hours. On a remote-controlled interface it always had to be clear which item the viewer had selected.

What was I responsible for?

  • I built the remote-control selection and navigation for Apple TV (tvOS) and Android TV.
  • For long 4K streams, I worked around the limits of the devices' built-in video players.
  • We built the mobile, web and TV versions in a single Nx codebase.

Key decisions

  • Alternative

    The original link between the JavaScript code and the native parts

    Choice

    A pilot of the new architecture (Fabric/JSI) on complex animation paths

    Consequence

    About 30% less UI-thread blocking in the animations I measured.

  • Alternative

    The devices' built-in video players

    Choice

    I worked around their limits for long 4K broadcasts

    Consequence

    Stable playback on the TV apps through live 4K sessions of more than two hours.

Results

  • The platform's peak traffic exceeded 500,000 concurrent viewers.
  • In the animations I measured, the interface thread was blocked about 30% less.

When this matters to you

  • If your software handles video or live data, or runs on several kinds of device, I start from its performance at the design stage.

Links