Client Components — Complete Guide
Client Components — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of Next.js Tutorial on Toolliyo Academy.
On this page
Next.js Tutorial (LearnHub) · Lesson 7 of 100
Client Components
Beginner → Intermediate → Advanced → Professional
Beginner · 1 — Foundations · ~12 min read · Module 1: Next.js Foundations
Introduction
This lesson is part of the beginner section. We explain Client Components slowly, with examples you can copy and run. If something is unclear, read it twice — that is how everyone learns. Client Components run in the browser. Add "use client" at the top of the file to use useState, useEffect, onClick, and browser APIs. They still get server-rendered HTML first, then hydrate for interactivity. Lesson video play buttons, quiz timers, and theme toggles need clicks and local state — impossible in a pure Server Component.
Client Components is setup knowledge. Without it, LearnHub will not run. Spend time here until npm run dev works without errors.
When will you use this?
You need this before writing any Next.js code — same as installing Node.js before opening a project.
- Every React/Next.js job expects you to run npx create-next-app and npm run dev on day one.
- Interviewers often ask you to explain the App Router folder structure and Server vs Client Components.
Real-world: Naukri-style job board
The Recruitment team building Naukri-style job board uses Client Components to add click handlers, video controls, and quiz timers in the browser. job seekers and recruiters never see the TypeScript files — they just get a fast, reliable job search, apply forms, and employer dashboards.
Production-style code
'use client';
import { useState } from 'react';
export function LessonCompleteButton({ lessonId }: { lessonId: string }) {
const [done, setDone] = useState(false);
return (
<button type="button" onClick={() => setDone(true)} disabled={done}>
{done ? 'Completed ✓' : 'Mark complete'}
</button>
);
}
What happens in production: In Naukri-style job board, getting Client Components right means job seekers and recruiters trust the job search, apply forms, and employer dashboards every day.
Lesson example (start here)
Copy this smaller example first. Once it works, compare it with the real-world code above.
'use client';
import { useState } from 'react';
export function MarkCompleteButton({ lessonId }: { lessonId: string }) {
const [done, setDone] = useState(false);
return (
<button
type="button"
onClick={() => setDone(true)}
disabled={done}
aria-pressed={done}
>
{done ? 'Completed ✓' : 'Mark lesson complete'}
</button>
);
}
Line-by-line walkthrough
| Code | What it means |
|---|---|
'use client'; | Marks this file as a Client Component — can use useState, onClick, and browser APIs. |
import { useState } from 'react'; | Imports React — needed for JSX and hooks in Client Components. |
export function MarkCompleteButton({ lessonId }: { lessonId: string }) { | Named export — reusable function or component. |
const [done, setDone] = useState(false); | React state hook — only works in Client Components (file needs "use client"). |
return ( | Returns JSX — what the user sees in the browser. |
<button | Part of the Client Components example — read it together with the lines before and after. |
type="button" | Part of the Client Components example — read it together with the lines before and after. |
onClick={() => setDone(true)} | Part of the Client Components example — read it together with the lines before and after. |
disabled={done} | Part of the Client Components example — read it together with the lines before and after. |
aria-pressed={done} | Part of the Client Components example — read it together with the lines before and after. |
> | Part of the Client Components example — read it together with the lines before and after. |
{done ? 'Completed ✓' : 'Mark lesson complete'} | Part of the Client Components example — read it together with the lines before and after. |
</button> | Part of the Client Components example — read it together with the lines before and after. |
); | Part of the Client Components example — read it together with the lines before and after. |
How it works (big picture)
- "use client" marks the boundary.
- useState remembers done between clicks.
- Server Components can import Client Components — not the reverse for children that need server data passed as props.
Do this on your computer
- Create components/MarkCompleteButton.tsx with "use client"
- Import it into a Server Component page
- Click and confirm state toggles
- Open React DevTools and find the component
- Read the real-world section and name which part of LearnHub uses this topic.
- Run the example locally with npm run dev and confirm the same behavior.
- Change one value in the example (route, text, or course id) and predict what will happen before you save.
Experiments — try changing this
- Change a string or route in the example and save — watch the browser update.
- Break the code on purpose (remove a bracket), read the error overlay, then fix it.
Remember
"use client" = browser interactivity. Use for state, effects, and event handlers. Keep Client Components small — leaf nodes in the tree.
Common questions
Can Client Components fetch data?
Yes with useEffect, but Server Components are preferred for initial data.
How long should I spend on Client Components?
Until you can explain it in your own words and run the example without looking at the answer. Beginners often need 30–60 minutes per new concept; setup lessons may take one afternoon.
What if I get stuck on Client Components?
Re-read the line-by-line walkthrough, check the terminal and browser overlay for errors, and compare your code character-by-character with the example. Search the exact error text — someone else had it too.
Where is Client Components used in real jobs?
See the real-world section above — the same pattern appears in LMS, e-commerce, SaaS, and dashboards. Interviewers ask you to explain it using one concrete example.