0
Challenge · 61Architecture & State
Global State Concepts
Archused in ~90% of apps
Teams reach for Redux the moment two far-apart components need the same data — then drown in boilerplate. The 2026 fix isn't a bigger store: it's realizing that most of what you call "global state" is actually a cache of server data, and only a thin slice is true client state.
Core idea. Split your state by where the source of truth lives: SERVER state is a remote-owned cache you keep fresh (use TanStack Query), CLIENT state is app-owned UI your code fully controls (use useState / Context / Zustand). Choose the tool from that split — don't default to Redux.
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
UNSORTED — pick a bucket for each
List of posts from /api/posts
The logged-in user's profile
Search results for a query
Is the sidebar open?
Dark-mode theme toggle
Which modal is currently open
Server state
a cache of data you don't own
empty
Client / UI state
state your app fully owns
empty
Each chip is a piece of "global state." Decide: is it a server cache, or true client state?
0/6 guessed right
↑ play a little first, then dig in