The Dark Art of Native APIs
summary
Shows concrete React Native bridge code and how Objective‑C/Swift native modules actually move heavy work off the JavaScript/main thread. Implements image and video processing as native components, measures CPU and frame handling (mentions 1080 frames and CGPoint/CGFloat math), walks through Xcode and tooling, and demos a hello‑world native component up to an integrated app. Presents which calls are synchronous versus async and what breaks or works in practice.
AI-written summary · about
chapters (13)
- 0:00Introduction to native APIs for JavaScript developers
- 3:00Why JS devs struggle with native APIs
- 6:12Hidden costs of JS-native bridges
- 9:49Performance pitfalls in native APIs
- 13:42Debugging native APIs examples
- 17:24Objective-C and Swift: Key differences for JavaScript developers
- 21:59Modular native components for mobile
- 25:54String handling in native APIs
- 29:43UI components in native dev
- 33:44Dictionaries and pointers in native APIs
- 36:52Pointers and memory in native code
- 40:10Extending React Native with native views
- 44:01Q&A
related talks
53mHow React-Native shapes the way we think about native apps
27mBuilding high quality mobile apps with React Native
26mReact Native: Under the Hood
28mReact Native Architecture Overview
40mKeynote: Building React Native
37mGetting to the Native in React Native
41mReact Native - A native love story
42mReact Native & Swift: best friends forever
