Frontend
A Mental Model for Server Components
Where the boundary goes, why 'use client' is a leaf concern, and how I stopped over-thinking the App Router.
Apr 2, 20261 min read
Server components confused me until I flipped my default. Now I assume everything is a server component and only reach for the client when a piece of UI genuinely needs the browser.
Push 'use client' to the leaves
The mistake is marking a whole page as a client component because one button needs state. Instead I keep the page on the server and extract the interactive bit into its own small client component, so the heavy rendering stays on the server.
Building something in this space?
I take on select builds when the work is worth doing right.