QtinUse - Developing the Netflix TV/Movie Streaming Service with Qt
summary
Netflix implements a server-driven dynamic UI using QtWebKit and a JavaScript bridge to embed DRM, auth and video player APIs into devices, choosing Qt over NPAPI and Chromium for faster integration and thread-safe signal/slot marshalling. Co-developed a texture mapper with Nokia to enable accelerated compositing and raise animations from ~1 fps to ~30–60 fps on mid/high hardware. Testing shows a 40% increase in on-screen viewing when personalized lists appear on TVs; low-end RAM and flash footprint remain the main constraints.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:12About Netflix
- 1:13Netflix subscriber numbers
- 1:46Consumer electronics
- 2:03Dynamic UI
- 2:41Innovation Curve
- 3:29Dynamic User Interface
- 4:48History
- 5:54AB Testing
- 9:54Dynamic UI Options
- 11:09HTTP Live Streaming
- 16:38Netflix SDK
- 17:40Netflix Dynamic UI
- 20:45QtinUse
- 23:27CSS animations
- 25:07Why are CSS animations so heavy
- 25:59Accelerated compositing
- 28:00Texturemapper
- 28:53Textmap
- 29:17Status
- 30:14Challenges
- 32:13Path Forward
- 34:17Questions
related talks
32mQt and the web, where are we today?
22mBringing LG webOS and Qt to millions of smartTVs
27mQt and Qt Quick on the Freebox Player set-top box
24mQt's Web Offering- An Overview
49mScaling Qt from Desktop to Servers and Micro-controllers
27mCompanion apps and more second screen options with Qt
27mHow to Implement an Automotive Infotainment System using Qt Quick
50mHTML5 in QtWebKit