The Framework Wars Are Over (For Us)
We have built production applications in React, Vue, Angular, Svelte, Go, Python, and plain server-rendered stacks. Our cloud hosting platform Deplexo runs Go on the backend with React + Vite on the frontend. Our automation tools are Python. But for web-facing client projects — marketing sites, dashboards, SaaS frontends, e-commerce — we default to Next.js. Not because it is perfect, but because it consistently delivers the best balance of performance, SEO, and developer velocity for those use cases.
Server-Side Rendering Changes Everything for SEO
The single biggest advantage of Next.js over a standard React SPA is server-side rendering. When a search engine crawler hits a Next.js page, it receives fully rendered HTML — not a blank div waiting for JavaScript to load. This is not a minor distinction; it is the difference between ranking on page one and being invisible.
With React Server Components in Next.js 14+, this gets even better. Components that do not need interactivity never ship JavaScript to the client. The result is smaller bundles, faster Time to Interactive, and better Core Web Vitals scores — all of which Google uses as ranking signals.
For a client's e-commerce site we built last year, switching from a Create React App SPA to Next.js with SSR improved their organic traffic by 340% within three months. The content was the same; only the delivery mechanism changed.
Performance Is Not Optional
Every 100ms of load time costs conversions. Next.js gives us automatic code splitting, image optimization via the built-in Image component, font optimization, and static generation for pages that do not change frequently. These are not features we have to configure — they work out of the box.
The App Router's streaming and Suspense boundaries mean users see content progressively instead of staring at a blank screen. For data-heavy dashboards, this is transformative. Users get the shell and navigation instantly while data loads in the background.
Compare this to a traditional SPA where the entire JavaScript bundle must download, parse, and execute before the user sees anything meaningful. On a 3G connection — still common in many markets — that can mean 8-12 seconds of nothing.
The Full-Stack Sweet Spot
Next.js blurs the line between frontend and backend in the best way. API routes (or Server Actions in the App Router) let us handle form submissions, database queries, and third-party integrations without spinning up a separate backend service.
For many client projects — marketing sites, portfolios, blogs, simple SaaS apps — this means deploying a single application instead of managing a frontend, backend, and the API contract between them. Fewer moving parts means fewer things that break.
When a project needs a dedicated backend — high-performance APIs, real-time systems, complex infrastructure — we reach for Go or Python depending on the use case, with Next.js as the frontend layer. Our hosting platform Deplexo, for example, uses a Go backend for container orchestration and CI/CD, paired with a React + Vite frontend. Next.js is not the answer to everything, but it pairs well with whatever backend the project demands.
Developer Experience Drives Delivery Speed
Time is money, and Next.js lets our team move fast without cutting corners. Hot module replacement means changes appear instantly during development. TypeScript support is first-class. The file-based routing system eliminates boilerplate and makes the app's structure immediately understandable to any developer.
When we onboard a new team member to a Next.js project, they are productive within hours, not days. The conventions are clear: pages go in the app directory, layouts wrap their children, loading states and error boundaries have dedicated files. There is less architecture to debate and more building to do.
The Ecosystem Is Unmatched
Next.js sits at the center of the React ecosystem, which is the largest frontend ecosystem in the world. Need authentication? Clerk, Auth.js, or Supabase Auth all have first-class Next.js integrations. Need a CMS? Sanity, Contentful, and Payload all optimize for Next.js. Need analytics, monitoring, or feature flags? Every major tool supports it.
This matters because clients do not pay us to build authentication systems from scratch. They pay us to solve their business problems. A rich ecosystem means we spend time on what makes their product unique, not reimplementing commodity features.
Deployment Is a Solved Problem
Vercel (the company behind Next.js) makes deployment trivial — push to Git, get a preview URL, merge to main, go live. But Next.js is not locked to Vercel. We deploy on AWS, Railway, and self-hosted servers depending on client requirements and budget.
The OpenNext project has made deploying to AWS via SST or CDK nearly as smooth as Vercel. For clients who need to keep everything within their own AWS organization, this is a game-changer.
The Trade-Offs We Accept
Next.js is not without downsides. The App Router introduced significant complexity, and the mental model of server vs. client components takes time to master. Build times for large apps can be slow. The framework's rapid evolution means occasional breaking changes between versions.
We also acknowledge that Next.js is overkill for some projects. A simple static site might be better served by Astro. A highly interactive SPA with no SEO requirements works fine with Vite + React — which is exactly what we use for Deplexo's dashboard. Backend-heavy systems like Telegram bots, automation pipelines, and infrastructure tooling? That is Go or Python territory, no React needed.
But for the 70-80% of web projects our clients bring us — business applications that need good SEO, fast load times, dynamic content, and room to grow — Next.js is the right default. We pick the best tool for each job, and for web-facing work, that tool is usually Next.js.