Why We Moved to Next.js App Router in 2026.
Vishvajeet Shukla · tesit · July 17, 2026
Every new client project we ship now starts on the Next.js App Router. That wasn't always the default — here's what changed our mind.
Server Components cut real weight
Pages that used to ship a client-side data-fetching waterfall now resolve on the server before the HTML ever reaches the browser. For content-heavy marketing sites, that's a meaningful First Contentful Paint win.
Colocated data fetching
Fetching data next to the component that renders it, without a separate API layer for every page, removes a whole category of boilerplate we used to write by hand.
The tradeoffs
It's not free. The client/server boundary takes discipline to get right, and some third-party libraries still assume a client-only world. We've hit a few of those walls.
The App Router rewards architecture discipline — and punishes treating every component like a client component out of habit.
Net result: fewer moving parts for content-driven pages, and a clearer mental model for where state actually needs to live.