Thuta Learning
React Native
AdvancedMobile Developmentintermediate

New Architecture, Fabric, TurboModules & Hermes

React NativeLesson 20

What you'll walk away with

  • Explain the React and native-platform behavior of New Architecture, Fabric, TurboModules & Hermes
  • Test accessibility, failure, and lifecycle cases
  • Write maintainable, testable, and performant React Native

Evaluate New Architecture, Fabric, TurboModules & Hermes on release devices through startup, JS/UI frame rate, memory, networking, crash recovery, permissions, signing, and store requirements—not only a debug build. Recheck New Architecture and dependency compatibility on every upgrade.

Build a Complete Mental Model

Evaluate New Architecture, Fabric, TurboModules & Hermes on release devices through startup, JS/UI frame rate, memory, networking, crash recovery, permissions, signing, and store requirements—not only a debug build. Recheck New Architecture and dependency compatibility on every upgrade.

Apply It in Production React Native

Test an original New Architecture, Fabric, TurboModules & Hermes example on Android and iOS with small and large screens, font scaling, dark mode, keyboard and screen reader use, slow/offline networking, denied permissions, and background/foreground transitions. Use DevTools, tests, and a release build where relevant.

After This Lesson

text
React state update
  → React render
  → Fabric Shadow Tree (C++)
  → Commit + Yoga layout
  → Native view mount

JavaScript engine: Hermes V1
Native interface: JSI + TurboModules
Typed bindings: Codegen
You should see
A clear model of render, commit, mount, and JavaScript/native boundaries.

Try It Yourself

Test an original New Architecture, Fabric, TurboModules & Hermes example on Android and iOS with small and large screens, font scaling, dark mode, keyboard and screen reader use, slow/offline networking, denied permissions, and background/foreground transitions. Use DevTools, tests, and a release build where relevant.

Platform and Lifecycle Warning

Assuming one simulator's happy path proves every real-device, release-build, permission, accessibility, offline, and lifecycle path.

About the New ArchitectureReact Native

Easy traps

  • Assuming one simulator's happy path proves every real-device, release-build, permission, accessibility, offline, and lifecycle path.
  • Applying web CSS or DOM assumptions directly, leaking subscriptions, or mixing every platform difference into one component.

Hands-on Exercise

Test an original New Architecture, Fabric, TurboModules & Hermes example on Android and iOS with small and large screens, font scaling, dark mode, keyboard and screen reader use, slow/offline networking, denied permissions, and background/foreground transitions. Use DevTools, tests, and a release build where relevant.

You'll know it worked when: A clear model of render, commit, mount, and JavaScript/native boundaries.