The Default: Start with Server Components
You'll learn: Why Server Components should be your starting point in Next.js App Router, not an afterthought.
The New Default Mental Model
In Next.js App Router, every component is a Server Component by default. This is a fundamental shift from traditional React development where everything was client-side by default.
Think of it like electricity in your home: you assume the lights work without generators in every room. Only when you need portable power (a laptop, phone) do you add batteries. Similarly, start with Server Components—they're the grid. Only add 'use client' when you need the "portable power" of interactivity.
Why This Matters
Starting with Server Components means:
- Zero JavaScript by default — your component doesn't ship code to the browser unless it needs to
- Direct data access — fetch from databases, read files, call APIs without extra layers
- Smaller bundles — only interactive pieces add to your JavaScript payload
When you create a new component, don't reach for 'use client' immediately. Ask yourself: "Does this component need useState, event handlers, browser APIs, or context?" If not, leave it as a Server Component.
The Decision Point
Only add 'use client' when you encounter:
- Interactive features (buttons that respond to clicks)
- React hooks (
useState,useEffect,useContext) - Browser-only APIs (
window,localStorage) - Third-party libraries that require client-side code
Everything else? Keep it on the server.
Key Takeaway: In Next.js App Router, Server Components are the default foundation. Only opt into client-side JavaScript by adding 'use client' when you genuinely need interactivity or browser APIs—this keeps your app fast and your bundles small.