0
Challenge · 41Realtime, AI & Motion
View Transitions
UXused in ~42% of apps
Native page and element animations used to mean reaching for a heavy library and fighting React. React 19.2 ships a built-in <ViewTransition> that animates UI as it updates — but only if the update happens the way React expects. Get the trigger wrong and nothing animates, and you will swear the API is broken.
Core idea. React 19.2 View Transitions animate the DOM difference between two renders, but they only fire when the update is wrapped in a Transition (startTransition / useTransition) or driven by a Next.js navigation. A plain setState that isn't a Transition will update instantly with no animation, even with <ViewTransition> in the tree.
poke it, drag it,
try to break it
try to break it
no slides here.
you drive.
you drive.
Playground, this isn't a screenshot
keystrokes accepted: 0
URGENT · the input
setText(value) is never wrapped — the controlled value stays urgent so the box always shows your latest keystroke.
LOW-PRIORITY · heavy list60 rows
react-0
render-1
state-2
effect-3
memo-4
hook-5
fiber-6
lane-7
commit-8
queue-9
react-10
render-11
state-12
effect-13
memo-14
hook-15
fiber-16
lane-17
commit-18
queue-19
react-20
render-21
state-22
effect-23
memo-24
hook-25
fiber-26
lane-27
commit-28
queue-29
react-30
render-31
state-32
effect-33
memo-34
hook-35
fiber-36
lane-37
commit-38
queue-39
react-40
render-41
state-42
effect-43
memo-44
hook-45
fiber-46
lane-47
commit-48
queue-49
react-50
render-51
state-52
effect-53
memo-54
hook-55
fiber-56
lane-57
commit-58
queue-59
useTransition marks the heavy list update non-urgent: each keystroke commits the input first, the list catches up after (dimmed while isPending). Type fast — the box never lags.
↑ play a little first, then dig in