Syed Abbas Ali (Abby)
Full Stack Developer · Delhi, India
Mainframe: Next.js made SSR and API routes straightforward from day one.
React and Next.js are not really competitors. Next.js is built on top of React — it uses React for rendering components. The question isn't which one is 'better'. The question is whether your project needs the additional layer that Next.js provides.
I've built production projects in both. Here's how I actually think about the choice.
What plain React gives you
React handles one thing excellently: building UI components that update reactively based on data changes. It's a view layer. That's it.
When you use plain React without Next.js, you bring your own routing, your own data fetching strategy, your own server setup if you need one. This is actually powerful for certain use cases.
Single-page applications that run entirely in the browser — dashboards, internal tools, admin panels, anything where the user logs in and the entire experience is client-side — often don't need server rendering at all. React alone is sufficient, and adding Next.js would introduce complexity with no benefit.
Vite + React is the current default for client-side-only applications. Fast to develop, simple to deploy, excellent output for SPAs.
What Next.js adds and why it matters for most websites
Next.js adds server-side rendering, static generation, file-based routing, built-in image optimisation, API routes, and edge middleware on top of React.
The most important of these for business websites is static generation and server rendering. When someone searches for your business on Google and clicks a link, the page needs to be rendered and readable in milliseconds — before any JavaScript executes. React alone doesn't do this. A plain React SPA sends a blank HTML shell and then renders the page with JavaScript.
Next.js pre-renders pages at build time or on the server. The HTML that arrives in the browser is already populated. This is what makes Next.js sites faster for first-time visitors and more reliably indexed by search engines.
"99% of the business websites I build are public-facing, need to rank on Google, and need to load fast for first-time visitors. Next.js is the right tool for 99% of those projects."
— My actual decision-making process
The practical recommendation
Business website, portfolio, marketing pages, e-commerce storefront, SaaS landing page → Next.js. Every time.
Internal tool, logged-in dashboard, admin panel, real-time collaborative app → React with Vite.
The decision is almost never about developer preference. It's about what the page delivery model needs to be. Public pages that need to rank on search engines and load fast for strangers → server rendering. Private pages only logged-in users see → client-side is fine.
Final thought
If you're starting a new project and unsure which to choose, ask yourself: does this need to be discoverable on Google, and does it need to load fast for someone who has never visited before? If yes — Next.js. If the content is entirely behind a login — React alone is cleaner. I'm happy to give an opinion on a specific project if you reach out.
Syed Abbas Ali(Abby)
Full Stack Developer & Web Architect based in Delhi, India. 3+ years building websites and web applications for founders, startups, and growing businesses. I handle everything: design, frontend, backend, and deployment.
READY TO BUILD SOMETHING?
Full stack engineering, clean code, 6–7 day delivery. Let's talk.