Server and Client Components Learn the server/browser network boundary, choose Client Components for the right reasons, and avoid turning the entire frontend into a client island.
Server Components and Client Components The most important Next.js concept in Phase 03 is not routing. It is understanding that your component tree can cross a network boundary. Next.js uses Server Components by default in the App Router; Client Components are opt-in islands for browser capabilities and interaction.
render hydrate/interact
rendered output interactive JS
Figure 1 - Server and browser environments have different capabilities; use client marks where browser-side JavaScript is needed
Server Component by default A component file under the App Router is a Server Component unless a Client Component boundary applies. This lets static and server-rendered UI avoid sending unnecessary component JavaScript to the browser.
Good Server Component jobs • Compose mostly non-interactive UI. • Read server-side data later without exposing secrets to the browser. • Perform server-only work when appropriate. • Keep large dependencies or logic off the client bundle when no browser interaction is required.
What makes a Client Component necessary? Use a Client Component when the component needs browser-only capabilities or interactive React state/effects.
Need Client? Reason
useState/useEffect Yes Client hooks require browser-side React
window/localStorage Yes Browser APIs do not exist on the server
Later API server-state with TanStack Yes at Query client lives in browser context Query provider/query boundary
"use client";
import { useState } from "react";export function DemoCounter() {
const [count, setCount] = useState(0);return ( <button onClick={() => setCount((value) => value + 1)}> Count: {count} </button> ); }
The directive marks a client module boundary. It does not mean every component in the entire application must become client-rendered.
Keep the boundary small A common beginner response to a hook error is to put "use client" at the top of the root layout. That makes the error disappear by widening the client boundary, but it throws away a core architectural advantage. Move only the interactive portion behind a client boundary.
children
Serialization boundary Data passed from a Server Component into a Client Component must be serializable across the server/client boundary. This is another clue that the boundary is architectural, not just a syntax marker.
Do not confuse rendering location with API architecture Server Components can fetch directly from a data source in some applications. TaskFlow deliberately routes authoritative business data through NestJS later so business rules live in one backend. The fact that Next.js can access server resources does not require us to put domain logic there.
Mini exercise Create an interactive small button or disclosure control as a Client Component and import it into a Server Component page. Then explain why the page itself did not need use client.
Checkpoint • Server Component is the default in the App Router. • Client Components are for interaction/browser APIs/client hooks.
• use client creates a boundary; it is not a quality badge. • The smallest useful client boundary usually gives the clearest architecture. • TaskFlow keeps authoritative business rules in NestJS even though Next.js has server capabilities.
Server and Client Components matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Server and Client Components” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: route data → UI state → component tree → interaction → accessible feedback. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: A navigable TaskFlow web shell with route groups/layouts, server-first composition, selective client interactivity, and verified environment handling.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
if (query.isPending) return <TaskSkeleton />;
if (query.isError) return <TaskError retry={query.refetch} />;
if (!query.data.length) return <EmptyTasks />;
return <TaskTable tasks={query.data} />;Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Server and Client Components” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Build one component as a Server Component and identify exactly why it can remain server-only.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Leaking secrets through NEXT_PUBLIC variables
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.