React Native vs native: choosing the right app approach

Choosing between React Native and Native mobile development (Swift for iOS, Kotlin for Android) is one of the most consequential architectural and financial decisions a technology founder or engineering lead will make. The choice directly dictates your capital runway, team composition, release cadence, and the upper limits of hardware performance.

1. The Technical Architecture: Old vs. New React Native

Historically, criticisms of React Native centered on the "Asynchronous JSON Bridge." In the legacy architecture, JavaScript thread communications with native UI modules were serialized into JSON strings across an asynchronous bridge, causing dropped frames during intensive scroll events or high-frequency touch interactions.

With React Native's New Architecture (Fabric and TurboModules enabled by default), the bridge has been entirely eliminated:

• JavaScript Interface (JSI): Replaces the serialized JSON bridge with direct C++ host object references. JavaScript can invoke native C++ methods synchronously, delivering zero-latency native method dispatch.
• Fabric Concurrent Renderer: Integrates React 18/19 concurrent rendering directly with platform-native UI engines (UIKit on iOS, Android View hierarchy), enabling seamless prioritization of urgent user interactions.
• TurboModules: Native modules are loaded lazily on demand rather than eagerly initialized at app boot, significantly slashing initial launch time and resident memory footprints.

2. When Native Development is Strictly Required

Despite the rapid maturation of cross-platform ecosystems, native development remains the superior engineering choice in several specialized verticals:

1. Low-Latency Hardware Interfacing: Continuous real-time Bluetooth Low Energy (BLE) peripheral streaming, IoT firmware flashing, or bespoke audio synthesizers where sub-5ms buffer latencies are critical.
2. Intensive Computational Vision & AR: Deep integration with Apple ARKit, LiDAR sensors, or on-device computer vision models using CoreML/Metal where C++ pointer arithmetic dominates execution.
3. Complex Custom GPU Shaders: AAA mobile gaming, intricate particle simulators, or custom Metal/Vulkan graphics pipelines.

3. The Financial & Organizational Equations

For early-stage startups and growth businesses, the operational friction of maintaining two separate native teams often slows feature iteration to a crawl. If a business builds natively, every new feature requires:

• Two parallel feature specifications and UX adaptation meetings.
• Separate pull requests in Swift and Kotlin with platform-specific edge cases.
• Double the QA surface area and synchronized App Store submission tracking.

With React Native paired with a modern monorepo (such as Turborepo), companies can share business logic, API validation schemas (Zod), and authentication state between their web platform (Next.js) and mobile application (React Native / Expo), shrinking development hours by more than half.

4. Production Native Module Interop Example

When a React Native application does require deep native capabilities, developers are never locked out of the native platform. Writing a custom native module using TurboModules allows seamless integration with platform SDKs:

// Example iOS TurboModule implementation in Swift
import Foundation
import React

@objc(BiometricAuthModule)
class BiometricAuthModule: NSObject {
  @objc
  func authenticateUser(_ resolve: @escaping RCTPromiseResolveBlock, 
                       rejecter reject: @escaping RCTPromiseRejectBlock) {
    let context = LAContext()
    var error: NSError?
    
    if context.canEvaluatePolicy(.deviceOwnerAuthenticationWithBiometrics, error: &error) {
      context.evaluatePolicy(.deviceOwnerAuthenticationWithBiometrics, 
                            localizedReason: "Authenticate to access secure data") { success, evalError in
        if success {
          resolve(true)
        } else {
          reject("AUTH_FAILED", "Biometric authentication failed", evalError)
        }
      }
    } else {
      reject("UNAVAILABLE", "Biometrics unavailable on device", error)
    }
  }
}

5. Architectural Decision Matrix for CTOs and Founders

• Select React Native if: Your app is driven by REST/GraphQL APIs, user profiles, real-time messaging, payments, interactive dashboards, or media playback. You gain immediate access to both platforms and can iterate twice as fast on user feedback.
• Select Native if: Your core intellectual property lives in proprietary low-level hardware communication, real-time audio/video processing algorithms, or advanced custom graphics engines.