Re-architecting the ElevenAgents SDK for React Native
summary
ElevenLabs replaces a single monolithic context with separate, memoized context providers one context per concern, which stops unrelated components (e.g., a frequently updating volume panel) from re-rendering unnecessarily; the core becomes a platform-agnostic imperative JS client with a hooks-based React SDK layered on top, and the React Native package simply re-exports the React package with small audio injections to avoid duplicate implementations. A provider-list helper reduces provider-tree hell, and an upgrade migration skill automates breaking changes.
AI-written summary · about
chapters (13)
- 0:00Introduction to context rod
- 1:20React context re-rendering issue
- 2:46Problem with monolithic context
- 3:49Toy example of context problem
- 4:53Solution with split contexts
- 5:55Prototyping with agent test bench
- 6:58Separating context by concern
- 8:25Reducing provider tree complexity
- 9:06Architecting platform-agnostic SDK
- 9:47Live demo of SDK
- 10:51Before state of SDK usage
- 11:34Migration tool for breaking changes
- 12:14Conclusion and key takeaways
related talks
43mReact Native Panel With Various Speakers
01h 01mReact Native: A Better Way to Do Mobile
25mGoing Native
30mReact Native's New Architecture
31mRewriting a Large Hybrid App with React Native
28mReact Native Architecture Overview
27mBuilding high quality mobile apps with React Native
28mThe State of React Native
