React vs React Native: what’s actually different

React vs React Native: what’s actually different
  • #Mobile apps
  • #Web apps

React builds user interfaces that run in a web browser. React Native builds user interfaces that run as real iOS and Android apps. They share a way of writing components, and almost nothing underneath.

That one sentence answers most of the searches that lead here. The rest of this article is for people deciding something: which one a product needs, whether a React team can build a mobile app, and how much code can be shared between a website and an app. We build in both every week, so this is the version we give clients rather than the documentation summary.

The part that is the same

Both use the same mental model. You describe the screen as a tree of components, each component takes inputs and holds some state, and when the state changes the framework works out what to redraw. Hooks, props, context, the way you structure a feature: all of it carries over.

The language is the same too. JavaScript or TypeScript, the same package manager, mostly the same state management and data-fetching libraries. A developer who knows React can read a React Native codebase on the first day and understand what most of it does.

That is where the similarity ends, and it is why the names cause so much confusion.

The part that is different

What a component turns into. In React on the web, components end up as HTML elements in the browser’s page. In React Native they end up as native platform views: the same building blocks an app written in Swift or Kotlin would use. There is no browser and no HTML. A div becomes a View, a span becomes Text, and there is no such thing as an img tag or a link.

Styling. React Native uses a subset of CSS ideas written as JavaScript objects. Layout is flexbox, there is no cascade, no stylesheet inheritance beyond text, and no media queries in the usual sense. Web developers adjust quickly, but the habits from CSS do not transfer as-is.

Navigation. On the web, a screen is a URL and the browser handles history. In an app, navigation is a stack of screens, tabs and modals that you manage yourself, with gestures and transitions users expect from their platform. It is a different design problem, not just a different library.

Device access. Camera, location, push notifications, biometrics, Bluetooth, background tasks, files on the device. On the web, these are limited by what the browser allows. In React Native they are available, through libraries or, where necessary, through native code written for each platform.

Distribution. A website is live when you deploy it. An app goes through App Store and Google Play review, and users update on their own schedule, so several versions of your app are in use at once. That changes how you release, how you version your API and how fast you can fix a mistake.

The build. A React web project builds with JavaScript tooling. A React Native project also builds with Xcode and Gradle, needs signing certificates and store accounts, and has to be tested on real devices, including cheap Android phones. This is the part React developers underestimate.

Can a React developer build a React Native app?

Mostly, yes. The screens, state and business logic are where most of the hours go, and a strong React developer is productive there quickly.

What they will not have is the mobile half: release builds and signing, store submission, push notification setup, permissions, deep links, behaviour on poor connections, and performance on low-end devices. None of it is exotic, but each piece costs a week the first time and an afternoon after that. A team doing its first app should have at least one person who has shipped one before.

How much code can a website and an app share?

More than most people assume, less than the marketing suggests.

Shares well: API clients, data models and types, validation rules, business logic, state management, formatting and localisation. In a well-organised project this is a large share of the non-visual code, and sharing it means a rule fixed once is fixed everywhere.

Shares with effort: the visual components. Libraries such as React Native for Web and Expo’s web support let one set of components render on both, and for some products, internal tools in particular, that is a good trade. For a public-facing product, a website and an app usually want different layouts, different navigation and different interaction patterns, and forcing them into one component set tends to make both feel slightly wrong.

Our default is shared logic in one repository and separate interface layers. It keeps the expensive parts in one place without compromising either experience.

Which one does your product need?

The honest framing is that this is not a React question. It is a question about whether you need an app.

A website or web app is enough when people use the product occasionally, usually on a laptop, it needs to be found through search, and nothing about it depends on the device. Most B2B tools, dashboards, booking flows and content products start here, and many never need more.

An app earns its cost when people use the product daily or on the move, it needs to work without a reliable connection, it depends on the camera, location, sensors or background behaviour, or notifications are central to how it works. Field tools, consumer products built around a habit, and anything people carry with them belong here.

Both, in sequence, is common. A web app first to prove the product, then a mobile app for the users who use it most, with the logic shared between them. Building both at once doubles the surface you have to get right before you know which one your users prefer.

A progressive web app sits between the two. It installs from the browser, works offline to a degree and can send notifications, though on iPhone only after the user adds it to the home screen. It is a reasonable step when the budget is tight, and a poor fit when the product depends heavily on the device.

Why we use React Native for mobile

When a product does need an app, we build it in React Native by default, for the reasons in why we stopped building native apps: one codebase, one set of fixes, one release process. We are open about where Flutter is the stronger choice, and how we decide is in React Native or Flutter: how we actually choose.

On the web, the same team uses React and Next.js. That is not a coincidence. A product that may need both a web app and a mobile app is cheaper to build and maintain when one team shares one model of how the interface works, even when the two interfaces are different.

If you are deciding this now

Tell us what the product does and who uses it, and we will tell you whether it needs a website, an app or both, and in what order. That answer is worth having before anyone estimates anything.

Related reading

Next Article
Taking over someone else’s codebase: the first two weeks
Next Article

Let’s talk about your project

welcome@ideus.biz