React versus frameworks

What this means

React builds UI. Frameworks like Next.js add routing, server rendering, data loading patterns, deployment conventions, and full-app structure.

In beginner terms, this topic answers one practical question: "What should I write, and why does React care about it?" Do not try to memorize the syntax first. First understand the idea, then connect the syntax to that idea.

Why it matters

This distinction prevents confusion. When you learn Next.js later, you are still using React, but with more app-level tools around it.

When you build real React screens, this idea helps you decide where data should live, what the user should see, and what should happen after an interaction. That is why this lesson is part of the main path instead of being an optional detail.

Step by step

1. Notice the UI problem this topic solves. 2. Look at the smallest possible example. 3. Change one value and predict what should appear. 4. Run the example and compare the result with your prediction. 5. Use the practice task before moving on.

Small example

React component: <Profile />
Framework route: /profile

Common mistake

Do not blame React for every framework feature. Routing and server components are framework-level concepts in many apps.

Practice task

List three things React handles and three things a framework often adds.

Remember this

React is the UI layer; frameworks organize full applications.