Case Study · Media · Streaming

Dolby OptiView
Live sports. Same moment. Every device.

Premium live sports is a player + a low-latency pipeline + ads that do not desync the score. This engagement is integrating Dolby OptiView (Player, Streaming, Ads, Sports Intelligence) — not building a toy HLS page.

What shipped: OptiView Player on Web, iOS, and Android (THEO lineage), OptiView Streaming for low-latency / real-time, OptiView Ads / Ad engine for live insertion, REST and SDK hooks from dolby.io. Node.js glue for session and entitlements.

OptiView Player WebRTC / LL-HLS Web · iOS · Android
What we built Technology dolby.io
Immersive live sports streaming on multiple devices
Low latency
Live ads
Any device
Fan on phone + living-room stream
Same cue point. Player SDK, not three custom players.
dolby.io
Player Web · iOS · Android
Streaming Low-latency live
Ads Live insertion
Intel Fan engagement
What we shipped

One stream. Three official SDKs.

We do not maintain a fourth player. OptiView Player is the device layer. Our app shells auth, entitlements, and Sports Intelligence overlays.

Web player

OptiView Player in the match page. Quality switching, ads, real-time metrics.

Shipped

iOS SDK

Same stream in the club/league app. Background audio rules, not a muted WKWebView.

Shipped

Android SDK

ExoPlayer-class path via OptiView. Same ad markers as web.

Shipped
The problem

Three players is three outages.

Before OptiView, web used a patched HLS.js, iOS used AVPlayer with custom ads, Android lagged two seconds. Chat said “goal” while the phone was still in midfield.

  • Latency driftPhones 8–12s behind the bar TV. Bets and chat died.
  • Ads broke the live edgeVOD-style prerolls on a live match.
  • No QoEOps learned about rebuffering from Twitter.
One real run

Kick-off · Sunday 16:00

  1. 15:58 — Player SDK joins the OptiView Streaming session. Entitlement from our Node.js API.
  2. 16:12 — Live ad break via Ad engine. All devices hit the same cue.
  3. 16:41 — Goal. Sports Intelligence marks the spike. Overlay stays in sync.
  4. FT — QoE metrics in the console Dolby already documents — not a homemade beacon.
Topic by topic

Streaming work, topic by topic

01 · Player

Official SDK

Before

Forked HLS.js.

After

OptiView Player on web, iOS, Android.

02 · Latency

Shared moment

Before

12s behind the stadium.

After

OptiView Streaming / real-time path.

03 · Ads

Live insertion

Before

Preroll that pauses the match.

After

OptiView Ads + Ad engine.

04 · QoE

Metrics

Before

Guessing from complaints.

After

Real-time viewer metrics from the player.

05 · Auth

Who can watch

Before

A leaked m3u8.

After

Node.js session tickets. Player requests with tokens.

06 · Intel

What kept fans

Before

Heatmaps in a slide.

After

Sports Intelligence on engagement dips.

Technology (from the live product)

Dolby OptiView SDKs. Our app is the shell.

Technology is taken from dolby.io / OptiView: Player (THEO Technologies lineage), Streaming, Ads, Ad engine, Sports Intelligence. We write the product shell in React (web) and native mobile, with Node.js for entitlements — we do not reimplement a CDN.

Source: dolby.io (OptiView Player, Streaming, Ads, Sports Intelligence; NFL+ and club quotes on the public site).

OptiView Player THEO WebRTC / LL-HLS iOS SDK Android SDK OptiView Ads Node.js
OptiView Player

Web, iOS, Android. Cross-platform compatibility is the vendor’s job.

OptiView Streaming

Low-latency live so chat and video share a moment.

Ads + Ad engine

Broadcast-quality insertion on live, not VOD hacks.

Node.js shell

Entitlements, start session, map user → stream.

Outcomes

What changed after go-live

Same second

Phone and pub TV are in the same moment.

Ads that do not desync

Breaks are cue-aligned.

QoE is a graph

Rebuffers are tickets, not tweets.

Build yours

Need live sports on real players?

OptiView SDKs + your shell. That is the Dolby.io shape.

Start a conversation Back to portfolio