In short
- The React team deprecated Create React App in February 2025 and now tells people starting a new app to use a framework such as Next.js (React blog).
- In Stack Overflow's 2025 survey, 48.7% of respondents used Node.js, 44.7% React and 20.8% Next.js, so the back end you learn sits under most of the front end you already know.
- Next.js 16 needs Node.js 20.9 or later and makes params and cookies async, so tutorials written before October 2025 will mislead you on details (Next.js blog).
- Next.js 16.4, out in October 2026, turns on Cache Components by default for new apps, and the team says it becomes the default in Next.js 17.
- 84% of developers use or plan to use AI tools, but 66% name answers that are 'almost right, but not quite' as their top frustration (Stack Overflow 2025), so checking AI output is part of the skill.
If you already write React and want to build the whole app yourself, a sensible Next.js course roadmap in 2026 has six stages: firm up JavaScript and TypeScript, learn plain HTTP with Node and Express, model data in a database, move to the Next.js App Router, add a GenAI API once you have a server and logins in place, then deploy. At eight to ten hours a week, plan on six to nine months to reach a deployed app you can explain line by line. GenAI comes late on purpose. The API key, the prompts and the checks on the model's answers all live on the server, so you need to understand the server first.
This note opens a four-part series, "Ship one product", which ends with something published.
Why the path now runs through a framework
For years the advice was "learn React with Create React App, then add a back end later". That advice has expired. In February 2025 the React team deprecated Create React App for new apps and said: "We recommend creating new React apps with a framework", naming Next.js, React Router and Expo 1. Their rule of thumb: if your app needs routing, you probably benefit from a framework 1.
The back end is not a niche add-on either. In Stack Overflow's 2025 survey, 48.7% of respondents used Node.js and 44.7% used React; Next.js was at 20.8% and Express at 19.9% 2. Those are self-selected survey answers, not job counts, but they show the stack is common.
One honest caveat about the "M" in MERN. The same survey shows PostgreSQL used by 55.6% of respondents and MongoDB by 24% 2. MongoDB is a fine first database for a JavaScript developer, because documents look like the objects you already handle. Learn data modelling properly, so that switching to SQL later is a matter of syntax.
The roadmap at a glance
The weeks below assume eight to ten hours a week alongside a job. They are estimates from teaching this material, not a promise. Solid JavaScript shortens the first two stages; little back-end experience lengthens the third.
| Stage | What you learn | Rough time | What you build | You're done when |
|---|---|---|---|---|
| 1. Language | Async JavaScript, modules, TypeScript types | 3–5 weeks | A typed React app that calls a public API | You can explain a promise chain and type a component's props |
| 2. HTTP and Node | Express, REST, auth, tests | 5–7 weeks | A notes API with sign-up, login and tests | A teammate can call your API from Postman without asking you |
| 3. Data | MongoDB, Mongoose, indexes, relations | 3–4 weeks | The same API on a real database | You can say why a query is slow and fix it |
| 4. Next.js | App Router, Server Components, Route Handlers, Server Actions, caching | 5–7 weeks | The notes app rebuilt in Next.js | You can say which code runs on the server and which in the browser |
| 5. GenAI | Calling a model API, prompts, retrieval, guarding inputs and outputs | 4–6 weeks | A "summarise my notes" feature | The feature fails safely when the model is wrong |
| 6. Ship | Environment variables, Docker, CI, logs | 2–4 weeks | The app live on a public URL | A stranger can sign up and use it |
Stages 1 to 3: the parts React developers skip
Most React developers can build screens. Fewer can explain what happens between the click and the database. Express is still a good teacher here because it keeps HTTP visible: a request comes in, middleware runs, you send a status code back.
Write tests, even a handful. An API with login is the first thing you build where a mistake leaks someone else's data. Then move it onto MongoDB and add an index you can measure.
Stage 4: what a Next.js course should teach in 2026
This is the stage where a Next.js course earns its place, and where old tutorials do the most damage. Next.js 16, released in October 2025, requires Node.js 20.9 or later, makes params, cookies() and headers() async, renames middleware.ts to proxy.ts and makes Turbopack the default bundler 3. A 2023 video shows none of that.
The caching model has also changed twice. Next.js 16 made caching opt-in through the "use cache" directive 3. Next.js 16.4, released in October 2026, turns Cache Components on by default for every new create-next-app project, and the team says it will become the default in Next.js 17 4. Learn the current model; skip the older implicit caching unless you maintain an old app.
Pick a Node.js LTS line and stay on it. Node 24 moved to maintenance this month, and Node 26 is scheduled to enter LTS at the end of October 2026 5. From Node 27, every release line will become LTS 5.
The milestone is one question: for each file, does it run on the server, in the browser, or both? Once you can answer without guessing, move on.
Where the GenAI API enters
GenAI enters at stage 5 because it depends on everything before it. A model API call needs a private key, and that key must never reach the browser. In Next.js the usual place is a Route Handler, a route.ts file under app/ that reads the key from an environment variable and forwards the request; the Next.js team calls this pattern a "Backend for Frontend" 6. That post is from February 2025, so check the current docs for details, but the principle holds.
The second reason is security. OWASP's top risk for LLM applications is prompt injection: input, including text inside a document the model reads, that changes the model's behaviour in ways you didn't intend 8. Its advice is engineering advice: give the model the least access it needs, keep a human approval step for risky actions, and check the model's output with ordinary code 8. OWASP also says no prevention method is known to be fully reliable 8. That list dates from late 2024; it is still where most teams start.
Build one feature, not a chatbot for its own sake. "Summarise my last ten notes" is enough. It forces you to fetch from your database, send a prompt, stream the answer and handle failure.
TTFA's MERN & Next.js with GenAI programme follows roughly this order, with the GenAI module after MongoDB and Next.js and before deployment.
AI coding assistants along the way
You will use AI assistants at every stage, and you should. In Stack Overflow's 2025 survey, 84% of respondents used or planned to use AI tools, and 50.6% of professional developers used them daily 7. The same survey found 45.7% distrust the accuracy of AI output, and 66% named answers that are "almost right, but not quite" as their biggest frustration 7.
That "almost right" is why the roadmap is staged. An assistant will happily write a 2023-style Next.js page or an Express route with no input validation. You can only catch that if you learnt the stage it belongs to.
Common wrong turns
- Starting with the AI feature. Without a server and a database, there is nothing for the model to work on and nowhere safe to keep the key.
- Collecting tutorials instead of shipping one app. Rebuild the same notes app at stages 2, 3 and 4 to see what each layer changed.
- Deploying only at the end. Deploy at stage 4 too; build errors are easier on a small app.
- Skipping tests and logs. Interviewers ask how you'd know something broke.
What to do with this
Pick the stage you're actually at and build its project before reading further. Keep a short README for each stage: what you built, what broke, what you changed.
The next note in this series is a decision note: React Native or Flutter in 2026, for a developer who has to choose one. It will cover how each fits a team that already writes React and TypeScript, and what you give up with either.
Frequently asked questions
Do I need Express if Next.js has Route Handlers?
It helps. Express shows HTTP plainly, which makes Route Handlers and Server Actions easier to reason about. Many teams also run a separate Node API alongside a Next.js front end.
Is a Next.js course enough without a database?
No. Next.js handles routing, rendering and server code, but you still need to store and model data. MongoDB fits the MERN stack; PostgreSQL is more widely used in Stack Overflow's survey.
When should I add GenAI to my project?
After your app has logins, a database and server code you understand. The API key and the checks on the model's output belong on the server, so that layer has to exist first.
How long does the whole path take?
At eight to ten hours a week, roughly six to nine months to a deployed app you can explain. Strong JavaScript shortens the early stages; little back-end experience lengthens the middle ones.
Sources
Checked on 23 Oct 2026. Where a figure comes from a company that sells training or hiring services, the note says so; treat those as directional.
- 1.React (Meta), Feb 2025 — Sunsetting Create React App react.dev/blog/2025/02/14/sunsetting-create-react-app
- 2.Stack Overflow, Jul 2025 — 2025 Developer Survey: Technology survey.stackoverflow.co/2025/technology
- 3.Vercel (Next.js blog), 21 Oct 2025 — Next.js 16 nextjs.org/blog/next-16
- 4.Vercel (Next.js blog), 6 Oct 2026 — Next.js 16.4 nextjs.org/blog/next-16-4
- 5.Node.js Release Working Group (OpenJS Foundation), Oct 2026 — Node.js Release schedule github.com/nodejs/release
- 6.Vercel (Next.js blog), 28 Feb 2025 — Building APIs with Next.js nextjs.org/blog/building-apis-with-nextjs
- 7.Stack Overflow, Jul 2025 — 2025 Developer Survey: AI survey.stackoverflow.co/2025/ai
- 8.OWASP Gen AI Security Project, Nov 2024 — LLM01:2025 Prompt Injection genai.owasp.org/llmrisk/llm01-prompt-injection/
Written by Shubham Patel
DevOps and full-stack engineer · teaches MERN, Next.js, React Native, DevOps
