Why we teach React with Next.js from day one
Plain React is a great start, but most teams ship with a framework. Here is why our Frontend path goes straight to Next.js, and what that changes in the classroom.

Every intake, someone asks the same question in the first week: shouldn't we learn plain React first, and only then a framework? It is a fair question, and for a long time our answer was yes. We taught components, props and state with a bare React setup, and introduced a framework in the last weeks of the course.
It isn't our answer any more. Over the last two years we moved the whole Frontend path to Next.js from the very first project, and the results convinced us. This article explains why, what we still teach the old way, and what trainees should expect.Teams ship frameworks, not libraries
When we looked at the job adverts our graduates actually applied to, the pattern was clear. Almost every frontend role in the region uses a framework on top of React. Routing, data loading, images, metadata and deployment are part of the daily work, not optional extras somebody else handles later.
Teaching React in isolation meant trainees learned to wire those pieces together by hand, then had to unlearn half of it on their first job. Learning them inside a framework from the start removes that gap.
Learning React inside Next.js is not harder. It is just closer to the job.
Components still come first
Moving to a framework does not mean skipping the fundamentals. The first two weeks are still about thinking in components: splitting a design into small pieces, passing data down with props and keeping state where it belongs. The difference is that those components live in real pages from the first day.
// app/page.js : a page is just a componentexport default function Page() { return ( <main> <h1>Hello, Tamkeen</h1> <CourseList /> </main> );}Trainees see the same React they would see in any tutorial. What changes is that the file they write is already a route, already rendered on the server and already one command away from being online.
What changes in the classroom
Pages and layouts arrive in week two, so projects feel real early instead of living in a single file.
Data fetching is taught where it belongs, next to the page that needs it, instead of in a pile of effects.
Deploying is a habit from the first project, not a scary step saved for the final week.
Code reviews focus on structure and naming, because the framework already decides the boring parts.
The biggest change is confidence. When the first project is online by the end of week three, trainees stop treating deployment as magic and start treating it as part of building.
What we still teach the hard way
Some things are worth doing by hand once. Before trainees use the framework's data helpers, they write one fetch with loading and error states themselves, so they understand what the helpers save them from. We do the same for forms and for client-side state.
async function loadCourses() { const res = await fetch("/api/courses"); if (!res.ok) throw new Error("Could not load courses"); return res.json();}The result
Trainees spend less time wiring tools together and more time building things they can show. Their final team project is a complete product site: several pages, real data, a design system and a deployment pipeline, reviewed pull request by pull request under the supervision of the trainer and a specialised committee.
If you are wondering whether to start with plain React on your own first, our advice is simple: don't wait. Start building pages. The fundamentals come with you.






