Why We Choose HTML5 for User Experiences on Devices
This is John Ciancutti, VP of Personalization Technology here at Netflix. As you know, last month we released a completely new user experience for Netflix on the PS3. I thought I would tell you about the technology choices we're using …
Context & Ripple Effects
John Ciancutti's post lands at the end of a pivotal month for Netflix: the company launched a $7.99 streaming-only plan and repriced its DVD bundles in late November, signed FilmDistrict for first-run films on December 1, and shipped a completely rebuilt PS3 experience in November. With investors already rewarding the DVD-to-streaming shift, Ciancutti is explaining the engineering logic underneath that expansion.
The argument also arrives months after Microsoft's IE team made the case for HTML5 video in April 2010, part of a broader industry turn toward web standards for media interfaces. Netflix choosing HTML5 for its device user experiences puts one of the biggest streamers squarely behind that direction.
First-order effects
- Netflix gains a single web-standard codebase for its interface across devices, meaning the new PS3 experience becomes a template other platforms can adopt rather than a one-off build.
- Device partners shipping Netflix get the same UI faster, reducing the per-device engineering cost that previously slowed feature parity between consoles and connected TVs.
Second-order effects
- Rival streaming services face pressure to match Netflix's pace of cross-device interface updates, since a write-once HTML5 layer lets Netflix iterate experiences without waiting on each platform owner's native tooling.
- Consumer-electronics makers evaluating which services to preinstall gain an argument for platforms that support modern browsers, shifting leverage toward devices whose runtimes make Netflix integration cheap.
Third-order effects
- If the pattern holds, TV interfaces consolidate around web standards the way mobile interfaces did, weakening the proprietary-SDK lock-in that console and set-top makers used to control the living-room experience.
- The remaining question flagged by the timing is whether standards bodies extend HTML5 far enough into protected video delivery itself — until then, Netflix's bet applies to the experience layer rather than the full pipeline.
The trend: Streaming services are converging their television interfaces on web standards like HTML5, trading per-device native builds for a single experience they can deploy everywhere.