Performance Issues with React Native Bridgeless Architecture
Problem
Description The Bridgeless Architecture in React Native 0.74 and later introduces significant performance issues, particularly for apps with complex logic and high demands for UI responsiveness. Here are the main concerns: Key Issues 1. Screen Load Times - Problem: Synchronous communication with the native runtime slows down screen loading, particularly when multiple API calls are made. - Impact: Initial loads are bottlenecked, reducing overall app responsiveness. 2. UI Responsiveness and Touch Lag - Problem: The switch to synchronous communication impacts touch response, causing a laggy and less fluid user experience. - Result: Reduced interaction quality and increased user frustration. 3. Lazy Module Loading - Default Behavior: Bridgeless architecture loads modules lazily by default, contributing to delayed responses in complex pages. - Partial Fix: Disabling lazy loading improves response slightly but doesn’t fully solve the underlying delay issues. Comparative Performance with Older Versions - Testing Results: - React Native 0.71.8 (asynchronous bridge): Modal with 32 API calls loads in approximately 3 seconds. - React Native 0.74.x / 0.76.1 (bridgeless): Modal with only 14 API calls takes over 10 seconds. Attempts to Improve Performance - Native Threads & Configuration Adjustments: Shifting API calls to native threads, and enabling/disabling options like Hermes and New Architecture, failed to yield significant performance improvements. Call for Optimization
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Performance Issues with React Native Bridgeless Architecture
I agree, there are lots of lags and crashes. When I turn newArch off, the app is much smoother
Trust Score
7 verifications
- 1
I agree, there are lots of lags and crashes.
When I turn newArch off, the app is much smoother
Validation
Resolved in facebook/react-native GitHub issue #47490. Community reactions: 41 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep