PROVIDER - native mobile apps written in React

React Native

React Native has been open source from Meta since 2015, emitting native mobile apps from JavaScript and React, with the Fabric and TurboModules architecture cutting bridge cost and Expo plus Hermes filling in tooling and performance; native upkeep, upgrade cost and tuning are the practical boundaries.

Programming Languages & Frameworks United States 2026.11.19
4.3pts

Detailed Notes

Pros 5 items

Meta open sourced it in 2015 to build native mobile apps with JavaScript and React syntax
The new architecture, Fabric and TurboModules, calls native capability through JSI, cutting bridge overhead by roughly 1 order of magnitude
1 codebase ships to both iOS and Android, with Expo unifying builds, previews and over-the-air updates
Community libraries cover more than 6 common needs including navigation, animation, camera and push
The Hermes engine brings faster start-up, cutting cold start by about 1/3, with lower memory use on mobile

Cons 4 items

Native modules and platform differences still need separate upkeep, and complex interactions often require Kotlin or Swift
Major version upgrades trigger chained dependency updates, so migration costs are real
Performance-sensitive work such as complex animation or very large lists needs dedicated optimisation
Debugging spans both JavaScript and native layers, making issues harder to isolate than in native code

Service Overview

React Native was open sourced by Meta in 2015, bringing React's component model to mobile: JavaScript logic drives native control rendering rather than hosting a web page in a WebView.

In the languages and frameworks category it represents the frontend-skill-reuse route, letting existing React teams deliver iOS and Android apps quickly.

Key Strengths

  • Skill reuse: React developers start immediately with familiar tooling and patterns
  • Native rendering: output uses platform-native controls, so interaction feels close to native
  • New architecture gains: Fabric and TurboModules reduce cross-language communication through JSI
  • Mature tooling: Expo covers builds, OTA updates and device previews
  • Large community: almost every common feature already has a library

Product Ecosystem

Framework and engine

The React Native core, the Hermes engine, the new architecture and the Fabric renderer.

Toolchain

Expo, the Metro bundler, the React Native CLI and Flipper for debugging.

Application areas

E-commerce and content apps, internal enterprise tools, and social or utility products that iterate quickly.

Limitations

  • Native upkeep: device capability and platform differences still need Java/Kotlin or Objective-C/Swift
  • Upgrade cost: major versions often bring chained dependency upgrades
  • Performance limits: complex animation and very long lists need optimisation or native components
  • Debugging depth: mixing JavaScript and native layers lengthens the path from symptom to cause

Use Cases

  • Content and e-commerce apps (★★★★★): lists, detail pages and payments are proven
  • Rapid validation and MVPs (★★★★★): a dual-platform prototype can appear in about 2 days
  • Internal enterprise apps (★★★★): forms and approval flows are efficient
  • Graphics-heavy apps and games (★★): prefer an engine or native stack

Pricing

Item Price Notes
React Native and Expo (open source) $0 Free and open source
Expo cloud builds Per build or subscription Free tier is limited
Store developer accounts 99 USD per year and 25 USD once Billed by Apple and Google

The framework is free; cost concentrates in cloud builds, accounts and native adaptation effort.

FAQ

  • React Native or Flutter? Choose React Native when the team already knows React, and Flutter when pixel-level consistency and custom rendering matter most.
  • Is native development required? Not for basic features, but camera, Bluetooth and payment work usually needs a native module.
  • Is performance sufficient? For ordinary business flows yes; complex animation and large lists need native components and tuning. More cross-platform options are under languages and frameworks.

Code Examples

A function component with state

import React, { useState } from 'react';
import { View, Text, Button, StyleSheet } from 'react-native';

export default function Counter() {
  const [count, setCount] = useState(0);

  return (
    <View style={styles.container}>
      <Text style={styles.label}>Count: {count}</Text>
      <Button title="Add" onPress={() => setCount(count + 1)} />
    </View>
  );
}

const styles = StyleSheet.create({
  container: { flex: 1, alignItems: 'center', justifyContent: 'center' },
  label: { fontSize: 20, marginBottom: 12 },
});

useState holds state, and StyleSheet.create separates styling from the component for reuse and optimisation.

A virtualised list

import { FlatList, Text, TouchableOpacity } from 'react-native';

export default function ItemList({ items, onPick }) {
  return (
    <FlatList
      data={items}
      keyExtractor={(item) => String(item.id)}
      renderItem={({ item }) => (
        <TouchableOpacity onPress={() => onPick(item.id)}>
          <Text>{item.name}</Text>
        </TouchableOpacity>
      )}
    />
  );
}

FlatList renders virtually, and keyExtractor supplies stable keys to avoid re-render churn.

Community & Resources

Visit React Native Website → https://reactnative.dev/
Visit Website ↗