From Electron to React Native
summary
Migrates Messenger desktop from Electron to React Native, reusing C++ addons via JSI and Turbo modules, replacing the web-based calling window with a native surface. Benchmarks on low-end Windows show electron boots ~3× slower; overall rollout yields ~50% startup time reduction, ~100 MB smaller installer, big memory drops and native crashes cut nearly in half while keeping feature parity. Practical work: code-mod conversion, native windowing modules, and generated C++ bindings.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:09Migrating from Electron to React Native
- 3:55Electron's architecture challenges
- 8:27Custom UI components in Electron
- 11:59Exploring Electron alternatives
- 13:24React Native vs Electron benchmark
- 15:09Launching React Native from Electron
- 16:34Calling experience migration
- 17:57Migration strategy
- 19:21Migrating native add-ons
- 21:49Final architecture benefits
- 22:52Performance gains
- 23:33React Native challenges
- 25:00Electron vs React Native
- 26:23Microsoft collaboration
- 27:04Q&A
related talks
24mTaking React Native to macOS
29mA practical approach to building truly native cross-platform applications at scale
25mGoing Native
19mBuilding For Desktops And Dual Screens
35mMigration Web (Angular) to Mobile Development (React Native)
28mCross-Platform React
01h 13mMigrating to React Native: A long-term retrospective
01h 01mReact Native: A Better Way to Do Mobile