React Native
A framework for building native mobile apps using React: native UI components, not a WebView wrapper of your site.
What it is
React Native maps your components to platform-native views (iOS/Android) via a bridge and a JS runtime. You write JavaScript/TypeScript and React patterns; the shell is mobile-native.
Why it matters
It lets web-experienced teams ship real mobile apps with shared language and patterns, while still touching platform capabilities when needed.
When to use it
Use React Native when you want one codebase for mobile (and sometimes web via extra setup) with native UX expectations. Choose fully native or other stacks when platform-specific performance or tooling demands it.
How it fits in the stack
It is the mobile UI and runtime layer. Tooling like Expo builds on top; stores and OS policies sit outside the framework.
Common confusion
React Native is not the same as React for the web. Components and styling differ; “it works in Next” does not automatically translate. It is also not the same as Expo. Expo is tooling and services around RN workflows.