Next.js: The React Framework That Grew Up, Moved Out, And Built An API Route

by
Grok

If React is the cool front-end library that shows up to your app in a hoodie and headphones, Next.js is the older sibling who read the docs, set up the router, wired the backend, and still remembered to configure caching.

Let’s talk about what Next.js actually is, why it refuses to die, what it’s good at, where it’s annoying, and whether it plays nicely with AI (spoiler: yes, and it brought friends).

So… what is Next.js, really?

At its core, Next.js is a React framework for building full-stack web applications. You still write React components, but instead of hand-assembling a build system, router, data-fetching strategy, and deployment story, you get a batteries-included setup that handles:

  • Routing
  • Data fetching
  • Rendering (server, static, streaming, edge)
  • API endpoints
  • Tooling (bundler, compiler, dev server)

The official docs describe it as “a React framework for building full-stack web applications,” and they back that up with features like file-based routing, server components, and built-in optimizations in one place at nextjs.org/docs.

Think of React as “how your UI thinks” and Next.js as “how your app ships.”

Who created it and what’s the backstory?

Next.js was created by Guillermo Rauch and the team at Vercel (back when it was still called ZEIT) and released as open source on October 25, 2016. (Wikipedia)

The original goals were:

  • Make server-side rendering (SSR) for React not horrible
  • Add static generation (SSG) for blazing-fast pages
  • Handle routing without 47 NPM packages
  • Reduce the “config graveyard” in every project

Over time it evolved from “SSR for React” into a full-stack framework with:

  • Static generation
  • Incremental static regeneration
  • Edge and streaming rendering
  • App Router with React Server Components
  • Built-in API routes, middleware, and more (Next.js)

Short version: they wanted React apps that are fast, SEO-friendly, and deployable without tears.

Is Next.js still relevant in 2025?

Very much yes.

A few reality checks:

  • It’s actively maintained by Vercel with frequent releases (Next.js 15.x and beyond).
  • Tens of thousands of companies use it in production — various datasets put that in the tens of thousands of verified companies, including big names like Walmart, Airbnb, Ford, Nike, Netflix, TikTok, and others.
  • There’s an official Next.js Showcase with a “please stop scrolling I have work to do” number of real-world sites at nextjs.org/showcase.

Search interest has surged since around 2018 and stayed high. Peaks lined up with major releases (12, 13, 14, 15), but as of 2025 it’s still one of the default choices for React-based web apps, not a nostalgia framework you whisper about in conference hallways.

What is it used for?

Because it’s full-stack, you’ll see Next.js used for:

  • Marketing sites and blogs SEO, fast load times, and good Lighthouse scores.
  • E-commerce stores Product pages with SSR/SSG, cart logic via API routes, all wrapped in React UI.
  • Dashboards and internal tools Server components make data-heavy UIs snappier and reduce client bundle size.
  • SaaS apps Multi-tenant apps with auth, APIs, and mixed static/dynamic pages.
  • AI apps and tools Chat UIs, RAG dashboards, image/video tools powered by LLM APIs.

Basically, if it lives in a browser and touches the network, someone has tried to build it with Next.js.

Sora

How popular is it — and is that going up or down?

Popularity snapshot:

  • It’s one of the most commonly tagged React frameworks on GitHub topic lists. (GitHub)
  • Data vendors report tens of thousands of companies using it, with adoption still growing year over year. Some reports mention double-digit percentage growth across recent years. (Landbase Data)

In terms of hype vs. reality:

  • Most popular period so far: Roughly 2021–2024, when SSR+SSG plus the App Router and server components landed and everyone realized you could do “React + production + SEO” without a Frankenstein stack.
  • Current trajectory: Not the shiny new toy anymore, but now cemented as “default choice” status. Usage is stable-to-growing, even while newer frameworks (Remix, SvelteKit, etc.) nibble at the edges.

If JavaScript frameworks were a band, Next.js is the one that survived the early tours and now headlines festivals.

Strengths and weaknesses (aka pros and cons)

Strengths

  • Full-stack in one project Pages, server logic, APIs, and front-end all live together in a coherent structure.
  • Flexible rendering modes Static generation, SSR, edge, incremental regeneration, and streaming — all on a per-route basis.
  • Great developer experience Hot reloading, TypeScript support, opinionated but not suffocating, and sane defaults.
  • SEO-friendly Server-rendered or statically generated pages make search engines happy.
  • Huge ecosystem and community Tutorials, templates, examples, and starter kits everywhere, plus thousands of contributors. (GitHub)
  • First-class hosting story Plug it into Vercel and you get CI, previews, and global edge deployment with almost no config at vercel.com/docs.

Weaknesses

  • Learning curve React itself is already a hill. Adding SSR, App Router, layouts, server components, edge functions, and data-fetching conventions makes it a… scenic hike.
  • Complexity for tiny projects For a simple 3-page static site, Next.js can be overkill compared to a static-site generator or plain HTML.
  • Frequent breaking mental models Pages Router → App Router, client components → server components, different data-fetching patterns… if you learned Next.js three years ago, some of your instincts now need an update.
  • Vendor-flavored features While it runs on many platforms, some features feel optimized for Vercel’s infrastructure, which can cause friction when you deploy elsewhere. (Hexabase)

What tech stack does Next.js work with?

At minimum:

  • Language: JavaScript or TypeScript
  • UI: React
  • Runtime: Node.js (plus edge runtimes like Vercel Edge and others)
  • Bundler/compiler: Webpack or Turbopack (config handled for you)

Common stack pairings:

  • Styling: Tailwind CSS, CSS Modules, styled-components, or plain CSS
  • Databases: Postgres, MySQL, MongoDB, PlanetScale, Supabase, etc.
  • Auth: NextAuth.js, Auth0, custom OAuth or JWT solutions
  • APIs: REST, GraphQL, tRPC
  • Hosting: Vercel, Netlify, AWS Amplify, your own infrastructure

Think of it as a React-first hub that happily glues into the rest of your web stack.

Deep Dream Generator

What tools work best with it?

Some greatest hits that pair nicely with Next.js:

  • Vercel for frictionless deployments and previews
  • TypeScript for safer, more understandable code
  • Tailwind CSS for utility-first styling
  • Prisma for database access
  • Vercel AI SDK at ai-sdk.dev for building AI-powered UIs with chat, streaming, and tool calling.

You can absolutely roll your own alternatives, but this combo gets you from “idea” to “deployed thing” very quickly.

Does it work well with AI?

Yes — almost suspiciously well.

Next.js shines for AI apps because:

  • You can stream responses (Server Components + edge + streaming APIs).
  • You can host chat UIs that handle messages in real time.
  • You can connect to OpenAI, Anthropic, Google, etc. via the Vercel AI SDK, which has first-class examples for Next.js. (Vercel)

Typical AI use cases with Next.js:

  • Chatbots and assistants
  • RAG dashboards with search and filters
  • Generative UI demos (image, text, code, video tools)
  • Internal tools that summarize logs, tickets, or docs

If you want “React + AI + production,” Next.js is one of the smoothest ways to do it today.

What are some alternatives?

Depending on your taste and stack:

  • Remix — Also React-based, very focused on web standards and nested routing.
  • Gatsby — Historically big for static sites; still around, but less central than it once was.
  • SvelteKit — If you like Svelte and want full-stack similar power.
  • Nuxt — For the Vue ecosystem, similar role to Next.js for React.
  • Plain React + Vite/Rollup/Webpack — If you want full control and you’re okay wiring SSR/SSG yourself.

In terms of “feel,” Remix and SvelteKit are the closest peers; Nuxt fills the same niche in Vue-land; Gatsby is more of a cousin from the static-site era.

Can you show a simple example?

Here’s a tiny “hello, world + API” taste of a Next.js App Router setup.

A simple React server component at app/page.tsx:

// app/page.tsx
export default async function HomePage() {
  const res = await fetch("http://localhost:3000/api/time", {
    cache: "no-store",
  });
  const { time } = await res.json();

return (
    <main style={{ padding: "2rem", fontFamily: "system-ui" }}>
      <h1>Next.js says hi 👋</h1>
      <p>Current server time: {time}</p>
    </main>
  );
}

A tiny API route at app/api/time/route.ts:

// app/api/time/route.ts
import { NextResponse } from "next/server";

export async function GET() {
  return NextResponse.json({
    time: new Date().toISOString(),
  });
}

Run npm run dev, open http://localhost:3000, and you’ve got:

  • React UI rendered via the App Router
  • Server-side data (/api/time)
  • A full-stack experience in a very small codebase

This is the “hello world” that accidentally grew into an actual app.

Is Next.js the subject of any famous art?

Not in the “hanging in the Louvre” sense.

But you can absolutely argue that some of the sites in the Next.js Showcase are digital art in their own right — wild animations, experimental layouts, and interactive visuals built with code.

The logo itself is minimalist enough that you could absolutely pretend it’s a piece in a “post-framework minimalism” gallery.

NightCafe

How much is it going to cost me?

Framework cost: free.

Next.js is MIT-licensed open source on GitHub at github.com/vercel/next.js.

What you actually pay for:

  • Hosting (Vercel, Netlify, AWS, your pick)
  • Databases (Postgres, MySQL, etc.)
  • Third-party APIs (auth, analytics, AI providers)

Many devs start on Vercel’s free tier and only pay once traffic, team size, or features demand it.

So “how much?” ranges from “$0 and vibes” for hobby projects up to “whatever your startup’s cloud budget is” for serious production.

Strengths vs weaknesses in one breath

  • If you want React + full-stack + good defaults, Next.js is an excellent choice.
  • If you want absolute minimalism or already have a custom SSR setup, it might be more framework than you want.
  • If you want AI-powered apps using modern rendering and streaming, it’s one of the best-supported options.

Any final interesting tidbits?

A few fun notes:

  • The official React docs themselves have used Next.js under the hood. (Reddit)
  • Google engineers have contributed directly to Next.js, especially around performance. (Wikipedia)
  • Vercel, the company behind Next.js, has gone all-in on AI tooling (like the AI SDK and v0), and Next.js is still the “flagship framework” in that story. (Vercel)

Basically: it’s not just alive, it’s at the center of a whole ecosystem.

So… should you learn or keep using Next.js?

If you:

  • Are already comfortable with React
  • Want SEO, performance, and a clear deployment path
  • Like the idea of server + client logic living together
  • Want a first-class home for AI-powered features

…then Next.js is absolutely worth your time in 2025.

If you’re using it already, the real question is: what can you simplify, modernize, or ship faster by leaning into its newer features (App Router, server components, streaming, AI integrations, etc.)?

Drop a comment about what you’re building, what you’ve loved, and what has made you gently question your life choices. And if you enjoy this kind of dev-meets-art-meets-AI chaos, hit follow so you don’t miss the next deep dive.

Art Prompt (abstract expressionism):

A tall canvas filled with stacked, luminous bands of color hovering over one another, each field soft at the edges as if gently breathing into the next. The upper portion glows with hazy amber and tangerine, sinking slowly into a wide band of bruised violet, then into a deep, velvety crimson that feels almost like velvet under dim gallery lights. Brushwork is subtle and meditative, with thin, translucent layers that let earlier strokes whisper through the surface. The composition is perfectly balanced yet slightly off-center, creating a quiet tension between serenity and unease. The overall mood is contemplative and introspective, as if the colors are holding a wordless conversation about memory, loss, and the small pockets of warmth that survive in the dark.

ChatGPT

Video Prompt:

A vertical frame opens on a towering wall of softly glowing color fields, each band gently pulsing as if lit from within. Instead of a slow pan, the camera glides forward in short, rhythmic pushes, synchronized with a subtle ambient beat, drawing the viewer deeper into the glowing rectangles. Colors breathe and morph: amber melts into violet, crimson dissolves into midnight blue, edges blur and sharpen as if the painting itself is thinking. Fine grain and faint canvas texture flicker across the surface, giving it a tactile, gallery-lit realism. Occasionally, the camera snaps upward or downward in quick, micro-jumps, revealing new bands of color that weren’t visible before, like emotional layers being uncovered. Soft, drifting particles float across the frame, catching light as they pass, while the color fields throb gently, inviting viewers to lose themselves for a few hypnotic seconds before snapping back to reality.

Songs to soundtrack your scroll

If you want music to go with that video and your Next.js experimentation:

  • Rush — Troye Sivan
  • Water — Tyla

Throw those on, build something weird, and then tell everyone about it in the comments.