One Player for Smart TV and Web. What Could Go Wrong?
summary
Describes how Okko extracted its video player into a separate product and organized teams per platform, then adapted a single video player/SDK to work on both classic web browsers and Smart TV platforms. Covers the architectural changes, specific decisions made, and the practical experience of aligning the SDK and development process across those two platform types.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:46About me
- 2:48Supported platforms
- 4:56Merging teams
- 5:40Modern video playback
- 7:03Logic duplication
- 8:09Unified SDK goals
- 9:14SDK development start
- 11:02Smart TV integration stages
- 12:30Moving players issues
- 14:10Player state management
- 16:43Tizen interface
- 17:47Async lifecycle
- 18:53SDK integration
- 20:23SDK publishing
- 21:27Player error handling
- 22:33Solving errors
- 23:14Event tracking
- 24:38Results
- 25:40Q&A
related talks
18mBuilding a scalable, multi-platform OTT app for India
19mTV Apps in the Wild
40mAlso develop for TVs (AppleTV and AndroidTV)
20mA 4-Year Retrospective : Lessons Learned from Building a Video Player from Scratch with React Native
37mCreating Engaging Android TV and Fire TV Apps with Native and Cross-Platform Tools
38mBuilding a Video Player from Scratch with React Native
42mLive Panel: Cross Platform Product Development
05mLightning talk: BikeShed - JavaScript in and on tvOS