Start With Plain State Updates

For screens that render quickly, set state and let React do its work. Scheduling matters when one update is expensive enough that the user can feel it while typing.

Take a typical case, made up for illustration. A back-office product grid filtered 5,000 rows on every keystroke. Each one took about 150 ms to render, so characters appeared in bursts and the filter box felt sticky. Wrapping the grid in useDeferredValue fixed it, and also exposed an older bug: rows keyed by index, so an inline edit stayed on row 3 while the product in row 3 changed.

Fiber is the engine inside React that makes rendering interruptible and prioritised. You never call it directly, but it explains why transitions work, why keys matter, why render must be pure and why Strict Mode runs things twice. Below is the mental model, without the source code: units of work, render and commit phases, and lanes.

If typing lags on heavy screens
  • You wrote setState three times in a handler and saw exactly one re-render — and weren't sure why
  • You wrapped state in useTransition and the "urgent" updates still felt slow
  • You see "React detected an update during render" warnings and don't know what fiber phase that refers to
  • You've heard "React 18 added concurrent rendering" but couldn't explain what changed