Basics of Streaming: The Messy World of Streaming Devices

For consumers, streaming feels seamless. For services, it’s a minefield. Every device comes with its own operating system quirks, development costs, and political baggage, and no single OS owns the living room. From Samsung’s Tizen to Roku’s BrightScript, from Google TV’s branding shuffle to newcomers like TiVo OS, Whale TV, and Ventura, fragmentation isn’t just an annoyance. It is the tax every streaming service pays to stay accessible everywhere viewers hit “play.”

Smart TV vs. Connected TV: Same Same, But Different

Quick distinction:

• Smart TV: A television with a built-in operating system (Samsung = Tizen, LG = WebOS, etc.).
• Connected TV (CTV): Any television that streams internet content, including Smart TVs and dumb screens plugged into sticks, boxes, or consoles.

So yes, all Smart TVs are CTVs. But not all CTVs are Smart TVs. That nuance matters when you’re counting reach, planning ad buys, or explaining why your service behaves differently on an LG OLED versus an Xbox.

The OS Gauntlet

Unlike mobile, which settled into iOS and Android, the TV world is Balkanized. Services have to support all of these environments, each with its own code stack and quirks.

Apple

• Devices: Apple TV, iPhone, iPad
• Stack: Objective-C, Swift; tvML/tvJS for template apps
• Notes: Premium UX, FairPlay DRM required, small global share (~2–3%) but non-negotiable for Apple households.

Google (Android TV / Google TV)

• Devices: Sony, TCL, Hisense TVs; Chromecast (discontinued in 2024); Google TV Streamer; Android mobile
• Stack: Java, Kotlin, C++ via NDK
• Notes: ~6 percent global share. Google ended Chromecast hardware production in 2024 after selling 100M units, pivoting to the more premium Google TV Streamer. Casting technology lives on inside Android TV/Google TV and embedded into other OEM TVs like LG. Services benefit from app continuity, but Google’s control remains a sticking point.

Amazon Fire OS → Vega OS (and Beyond)

• Devices: Fire TV sticks and cubes, Fire Edition TVs, Fire tablets
• Stacks:
  • Fire OS (legacy): Forked Android (Java/Kotlin)
  • Vega OS (new): Linux-based, already powering Echo Show and Echo Hub devices, slated for Fire TV hardware in 2025
  • Kittyhawk project: Premium Fire tablets testing open-source Android builds
• Notes: Historically ~6% global share. In North America, Fire holds 12%. Amazon is hedging bets: Fire OS still matters today, but Vega could take over long-term. For services, supporting Fire now means chasing multiple targets, and publishers are already being courted to port apps to Vega.

Roku OS

• Devices: Roku sticks and boxes; Roku-powered TVs (TCL, Hisense, etc.)
• Stack: BrightScript + SceneGraph (XML)
• Notes: ~59% U.S. household penetration, ~6% global. Proprietary language creates unique dev cost. In North America, Roku leads with 34% of the OS market.

Samsung Tizen

• Devices: All Samsung Smart TVs since 2015 (earlier sets used Orsay OS)
• Stack: HTML5, CSS, JS (via Tizen Studio IDE)
• Notes: Largest global OS (~13%). Feature-rich but strict QA cycles.

LG WebOS

• Devices: LG TVs + 20 OEM brands
• Stack: HTML5, CSS, JS (Enact framework or legacy WebOS SDK)
• Notes: ~8% global share. Known for polished UI, but app QA can bottleneck.

Hisense VIDAA

• Devices: Hisense, Toshiba
• Stack: HTML5/JS (VIDAA SDK)
• Notes: ~8% global share. Rapidly scaling via affordable global TV shipments.

Vizio SmartCast

• Devices: Vizio TVs (U.S.)
• Stack: HTML5/JS; Chromecast built-in
• Notes: ~6% global share, but 12% in North America. Walmart is shifting its Onn TVs to Vizio OS, positioning it as a rising force in the U.S.

TiVo OS

• Devices: Vestel, Sharp (U.S. 2025), others in the EU
• Stack: HTML5/JS + TiVo discovery APIs
  Notes: Now in 40+ countries. In the UK, four of the top five retailers carry TiVo TVs. Bundled with TiVo One, an ad platform at 4M MAUs.

Whale TV (formerly Zeasn)

• Devices: 400+ OEM brands globally
• Stack: HTML5/JS; Whale OS 10 integrates FAST service Whale TV+
• Notes: 43M+ active TVs. Shifting from OEM-only to consumer brand.

Ventura (The Trade Desk)

• Devices: OEM partner TVs (launching 2025)
• Stack: Expected HTML5/JS + extended ad APIs (details TBD)
• Notes: First ad-tech-first OS. OEMs keep more ad revenue.

Consoles (PlayStation, Xbox, Switch)

• Devices: PS4/5, Xbox One/Series, Switch
• Stack: C++, C#, Unity/Unreal engines
• Notes: Certification is strict. Skew younger, higher-ARPU households.

Fragmentation Beyond Software

Screens add another layer of chaos:

• Resolutions everywhere: 720p, 1080p, 4K, 8K. Most apps are built at 1080p and scaled.
  
• Pixel density gap: iPhone ≈ 460 PPI; 55″ 4K TV ≈ 80 PPI. Bigger fonts and chunkier buttons are required.
  
• 10-foot UI: Nobody holds a TV. Menus must work across the room with minimum 20px fonts, bold icons, and high contrast.
  
• Overscan headaches: Some TVs still crop edges. Designers leave safe zones.

Pretty is not the goal. Legible and reliable is.

The Take

For streaming services, fragmentation costs real money and loyalty:

1. Dev cost: One “app” is really 8–10 builds, each tested separately.
   
2. Feature inconsistency: Dolby Vision here, absent there. Downloads on iOS, missing on Fire.
   
3. Churn risk: Bad experience on someone’s primary device equals cancellation.

And no one is dominating. Globally, Samsung’s Tizen leads with about 13 percent of the market (CTVMA, 2024). But zoom in on North America, and the story flips: Roku takes the top spot with 34 percent, while Samsung, Fire, and Vizio split most of the rest (Omdia, Q1 2025). That contrast is the bigger picture — fragmentation isn’t just about device type, it’s fractured by geography too.

Consumers see one Netflix icon. Behind it, services juggle ten different codebases to make it appear across Tizen, Roku, Fire, Vega, and beyond. That is the hidden cost of streaming video services: not just servers and content rights, but the grind of device support.

The services that treat device strategy as core, not an afterthought, are the ones that win loyalty in the living room.

Bottom Line

Fragmentation isn’t a problem to solve; it’s the reality of streaming. The winners aren’t those who avoid it; they’re the ones who master it.

What’s Next

In the next part of Basics of Streaming, we will shift from delivery to dollars. We will explore various monetization models, including subscription, transactional, ad-supported, and hybrid models. We will also break down how services optimize ad delivery, use server-side insertion, and design tiered pricing plans.