useState hook introduction in React - Step-by-Step Execution

Concept Flow - useState hook introduction

Component renders

↓

useState called

↓

State variable created with initial value

↓

Component JSX uses state value

↓

User triggers event

↓

setState called with new value

↓

React schedules re-render

↓

Component re-renders with updated state

↓

UI updates to show new state

The component renders and calls useState to create a state variable. When setState is called, React re-renders the component with the updated state, updating the UI.

Execution Sample

React

import React, { useState } from 'react';

function Counter() {
  const [count, setCount] = useState(0);
  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}

A simple counter button that shows a number and increases it by 1 each time you click.

Execution Table

Step	Action	State Before	State After	Rendered Output
1	Component renders first time	count: undefined	count: 0	<button>0</button>
2	User clicks button	count: 0	count: 0	<button>0</button> (before re-render)
3	setCount called with count + 1	count: 0	count: 1	Scheduled re-render
4	Component re-renders	count: 1	count: 1	<button>1</button>
5	User clicks button again	count: 1	count: 1	<button>1</button> (before re-render)
6	setCount called with count + 1	count: 1	count: 2	Scheduled re-render
7	Component re-renders	count: 2	count: 2	<button>2</button>
8	No more clicks	count: 2	count: 2	No change, UI shows 2

💡 Execution stops when user stops clicking; state remains at last updated value.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	After Step 6	After Step 7	Final
count	undefined	0	1	1	2	2	2

Key Moments - 3 Insights

Why does the component re-render after calling setCount?

Calling setCount schedules React to re-render the component with the new state value, as shown between steps 3 and 4 in the execution_table.

Why does the displayed number update only after re-render?

The UI updates only after React re-renders the component with the updated state, so the button shows the new count at steps 4 and 7.

Is the state variable 'count' changed immediately when setCount is called?

No, setCount schedules the update; the state variable changes on the next render, visible in the variable_tracker after re-render steps.

Visual Quiz - 3 Questions

Look at the execution_table at step 4. What is the value of 'count' and what is shown on the button?

A count is 1, button shows 1

B count is 0, button shows 0

C count is 1, button shows 0

D count is 0, button shows 1

💡 Hint

Check the 'State After' and 'Rendered Output' columns at step 4 in the execution_table.

At which step does React schedule a re-render after the user clicks the button?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look for 'Scheduled re-render' in the 'Rendered Output' column in the execution_table.

If the initial useState value was 5 instead of 0, what would be the button label at step 1?

A 0

B 1

C 5

D Undefined

💡 Hint

Refer to the variable_tracker 'After Step 1' value and initial useState value.

Concept Snapshot

useState hook creates a state variable and a setter function.
Syntax: const [state, setState] = useState(initialValue);
Calling setState(newValue) schedules a re-render.
Component re-renders with updated state.
UI updates to reflect new state value.

Full Transcript

The useState hook in React lets you add state to a functional component. When the component first renders, useState sets the state variable to the initial value. The component shows this value in the UI. When the user triggers an event, like clicking a button, the setter function updates the state. React then re-renders the component with the new state value, updating the UI. This process repeats each time the state changes, keeping the UI in sync with the state.