React Native Radio RNR 353 - Node-API Support for React Native with Kræn Hansen
Feb 6, 2026
Kræn Hansen, a developer who built SDKs and native integrations at Realm and MongoDB and now works on ElevenLabs' developer experience, breaks down Node-API for React Native. He explains what Node-API is and is not. He compares Node-API to JSI and TurboModules. He covers Rust and multi-language bindings, ABI stability, tooling benefits, and what still needs to be done for wider support.
AI Snips
Chapters
Transcript
Episode notes
Maintaining Realm's Multiple Native Bindings
- Kræn Hansen described learning React Native on the job at Realm and working on its C++ core database for years.
- He explained how maintaining multiple native bindings across engines became painful and motivated exploring alternative native APIs.
Choose Node API To Build Rust Native Modules
- If you want to write native modules in Rust, consider Node API because it's defined as a C API and easily callable from Rust.
- Use Node API bindings and generators to get a cleaner Rust developer experience than writing raw C++ JSI code.
Node API As An Alternative To JSI
- Node API can act as a lower-level replacement for JSI and TurboModules for library authors.
- Kræn recommended library authors could choose Node API instead of JSI to target multiple runtimes with one implementation.