Migrating to Fabric
summary
Fabric requires upgrading to React Native 0.68 and opt‑in flags (RCT_ENABLED on iOS, a Gradle boolean on Android), plus Android NDK to build the new C++ common core. Migration uses react‑native codegen with spec files named NativeComponent.js spec files (Flow or TypeScript), and moves native modules to turbo modules via JSI for zero‑serialization calls. Software Mansion ports show concrete work: screens, gesture‑handler and reanimated (reanimated v3 released) run on Fabric, yielding faster first render and lower memory.
AI-written summary · about
chapters (10)
- 0:00Introduction to Fabric
- 1:09New architecture overview
- 2:21Enabling the new architecture
- 5:04App migration and troubleshooting
- 7:05Migrating native components
- 10:51Turbo modules and JSI
- 13:27Library migration examples
- 17:39Migrating Reanimated
- 21:08Benefits and future of Fabric
- 24:26Conclusion
related talks
36mInside React Native's New Architecture: Fabric, TurboModule…
29mModernizing React Native’s JavaScript
01h 13mMigrating to React Native: A long-term retrospective
53mWhat's next for React Native and Expo
27mBringing the New React Native Architecture to the OSS community
28mBringing the New React Native Architecture to the OSS community
23mReact Native: 2022 & Beyond
20mThe past, present, and future of React Native