State management
also: state manager, state management library
How your app organizes, stores and updates the information it's remembering, so every screen shows the same, up-to-date data.
The patterns and tools that decide where application state lives, how components read it, and how it changes. On the frontend this ranges from built-in component state to libraries like Redux, Zustand or TanStack Query.
A shared family calendar on the fridge. Instead of everyone keeping their own notes, there's one place to check and update, so nobody double-books the car.
Agents often suggest adding a state management library. For a small app, built-in tools are usually enough. Knowing what it's for lets you ask whether the extra library solves a real problem.
Cart data is passed down through five layers of components. I suggest a small Zustand store for state management rather than adding Redux.
Do we actually need a state management library, or can React's built-in tools handle this? Explain the tradeoff before installing anything.
Mixing it up with state itself or with a cache. State is the data. State management is how you organize and update it. A cache is a saved copy for speed.