Server & Client Component Composition Keep Server Components as the default and hydrate only interaction islands
Phase 20 - Production Application UI Volume 06 - Professional Frontend
v
v
Phase 20 turns the secure full-stack foundation into a coherent, accessible application interface without moving business authority into the browser.
Server Components remain the default Next.js App Router pages and layouts are Server Components by default. They are ideal for protected page composition and initial API fetching. Client Components enter only where browser state, event handlers, lifecycle hooks, or browser APIs are needed.
Feature Server or Client? Why
v
v
Small `use client` component
v
Once a module is marked `use client`, its imported subtree becomes part of the client bundle boundary.
Serializable props Props crossing from Server Components into Client Components must be serializable. Do not pass server-only functions, database clients, or secrets into a client island.
Client Component is not “bad”
Interactive UI needs client JavaScript. The goal is not zero Client Components; it is deliberate boundaries so the browser receives only what interaction needs.
Server and Client Component Composition 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 Component Composition” 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: TaskFlow responsive shell with navigation, workspace context, task screens, loading/empty/error states, and accessible interactions.. 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 Component Composition” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Build workspace/board/task navigation with active state derived from routing rather than duplicated local state.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Only styling the success state
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.