Porting Your SDK To React Native
summary
Mux reuses a shared mux JavaScript core library and builds a thin wrapper around react-native-video, hooking onLoad/onProgress/play/seek events via a higher‑order component to dispatch normalized events. Porting surfaces concrete problems: missing window.performance.timing and platform.js so fixes use conditional guards and React Native’s Platform module, and cross‑OS callback differences remain. The SDK is in beta with a few customers in production; native AVPlayer/ExoPlayer hooking was rejected to avoid brittle coupling.
AI-written summary · about
chapters (11)
- 0:00Wprowadzenie
- 0:23Porting your SDK to React Native
- 1:35Mux Data: Analytics for Video New Relictels you how your servers are performing
- 2:27Startup time
- 7:16We Built an SDK for Every Video Player
- 8:50SDK Architecture
- 11:52Typical workflow for building a new web SDK
- 15:00Next: check player documentation
- 15:32Higher Order Component Pattern
- 20:05Benefits of alternative approach . We get to re-use SDKs that we already build and we
- 20:32Downsides of alternative approach . This is a little bit more philosophical, but from our SDK's perspective, the player that we're interacting with is react-native-video. The fact that react-native-video
related talks
38mBuilding a Video Player from Scratch with React Native
35mMigration Web (Angular) to Mobile Development (React Native)
01h 01mReact Native: A Better Way to Do Mobile
20mA 4-Year Retrospective : Lessons Learned from Building a Video Player from Scratch with React Native
01h 13mMigrating to React Native: A long-term retrospective
40mPushing React Native outside the comfort zone
24mIntegrating React Native into an existing native codebase
39mReact Native - Unleash the power of React in your device