Next.js or not: choosing your stack

We often get asked "Next.js or not?" as if there were one universal right answer. There isn't. There is your product, your team and your horizon. The rest is noise.

What your product has to do

A site that lives off search ranking does not have the same needs as an internal tool behind a login. Server rendering, SEO, load time, interactivity: we list the real requirements before naming a single technology.

The team that will maintain it

The best stack is the one your team can keep evolving without us. A brilliant technology that no one on your side masters is a debt, not an asset.

The right stack is the one you will still be able to evolve three years from now.

Often, the answer really is Next.js. Sometimes it isn't. What matters is having decided for good reasons, and being able to explain them.