What "Next.js" actually means now
Next.js stopped being a framework and started being a platform. That is worth understanding before the next project kickoff.
Five years ago "Next.js" meant pages, getServerSideProps, and a static export. In 2026 it means an opinionated full-stack platform that ships its own router, cache, image pipeline, font loader, deployment runtime, and increasingly its own data layer.
Why this matters for clients
Picking Next.js is no longer just a frontend choice. It's an architecture decision that ripples into hosting, caching strategy, and how the team thinks about data fetching. The defaults are good - but they are defaults, and they assume things about your traffic and team that may not hold.
What we discuss before picking it
Hosting target - managed runtime vs self-host. Caching expectations - opt-in vs opt-out. CMS integration - coupled or external. Team familiarity - not "can they learn it" but "can they ship without our help in six months."
The honest version
Next.js is excellent for what it's good at. It is not a generic React framework anymore. Treating it like one leads to projects that fight the framework and lose.