The Next.js App Router architecture that actually scales
How we lay out App Router projects: route groups, server and client boundaries, data fetching without waterfalls, caching, and where state really belongs.
- nextjs
- react
- architecture
- app-router
Every article here comes out of a real client build — the decision we had to make, what we picked, and what it cost us later. No listicles, no framework hype, no reposted release notes.
Longer pieces that cover a whole decision rather than a single trick — the closest thing we have to a written account of how we build.
Filter by the part of the stack you care about. Each article names the stack, the constraint and the outcome up front.
We do not run a mailing list. Tell us the stack you are working on and we will send the relevant write-up when it goes out — plus anything from the archive that saves you a week.
Most of these articles started as a client problem. If one of them describes yours, send us the details and we will tell you how we would approach it.
Replies within 4 business hours · No obligation · You keep the scope document