Skip to content

Technology

React

React is how we build surfaces you can reuse, test, and hand over. A page is a composition, not a one-off file.

react.dev

What it is

React is Meta's library for building user interfaces from components. It is the default way a large share of product teams describe a screen: state in, UI out, a tree of pieces you can reuse. Instagram, Facebook, WhatsApp Web, and a long list of dashboards are React applications.

It is not a website by itself. You still need routing, data, and a build. Next.js, Remix, and Expo sit on top. React Native takes the same idea to phones. The centre is the component model, not the file extension.

What it does

Teams use React for web apps, design systems, and anything with enough interaction that a static template becomes a fight. Marketing sites use it when the CMS and the product share a system. Internal tools use it because hiring for React is easy.

We build in React when the interface has states, not only pages. We keep the tree small. We do not fetch the world to render a heading.

Why we use it

The interface layer for sites, SaaS, and tools.

Server Components where they help, client only where the interface must move. Types on every prop that matters. A tenth page is a CMS choosing order, not a new invention. The preview is the product you can refuse.

If a new view starts in a blank file, the system was not a system.

Built on it

Meta

Facebook, Instagram, and WhatsApp Web are the original React proving ground.

Netflix

The web app is a well-known React surface.

Airbnb

A long-time React shop for the booking product and internal tools.

Discord

The desktop and web clients are React (and Electron).

The New York Times

Interactive desks and product surfaces ship a lot of React.

All platformsNext: Next.js

Tell us what needs to ship.

You use a working prototype before the production build goes ahead.