React asks you to describe the interface as a function of state, and then quietly handles the rest. Components return markup; props flow down; state changes trigger redraws.
In plain language
On the web, this term comes up when people talk about how pages, apps, and services are built or connected. React asks you to describe the interface as a function of state, and then quietly handles the rest. Components return markup; props flow down; state changes trigger redraws. If you are new to the field, the simplest mental model is this: a library for composing ui out of components. Read it once with that frame in mind, then come back and read it again, and that is usually enough for the rest of the entry to make sense.
An everyday picture
Think of React as part of the doorway between a person and a machine. People see the door (the page that loads, the button that responds) and barely notice the hinges. React is one of the hinges.
Where it shows up
You meet React in almost every website, app, and dashboard. The piece itself is invisible; what you notice is the page that loads, the field that updates, the screen that fits the phone in your hand.
A small example
Imagine the scene above. The role React plays is the one its blurb describes: a library for composing UI out of components. Every time a page loads or a button fires a request, ideas like this are quietly doing the work between the browser and the server.
Common misunderstanding
One line to take with you
React is part of the surface between people and machines. The user sees the result, never the seam.
Frequently asked
React is a library, not a full framework. It handles one job well: turning state into UI. Routing, data fetching, and server rendering are left to other tools, which is why React is often paired with a framework like Next.js or Remix that bundles those pieces together. The distinction matters in practice, because building a real app means choosing the surrounding tools yourself.
A component is one piece of the screen, such as a button or a card, and state is the data that piece holds, such as a like count. When the state changes, React redraws only the parts that depend on it. You describe what the screen should look like for a given state, and React works out which elements to update. Those two ideas, components and state, are enough to explain almost any React screen.
No. JSX looks like HTML, but it is a separate syntax that runs inside JavaScript and compiles down to function calls that build the DOM. The benefit is that a component can keep its markup and its logic in one place, so opening a single file shows you both what it draws and how it behaves. Treating JSX as plain HTML leads to confusion the moment you need to use a JavaScript expression inside it.