Frontend & browser·State, data and re-rendering
the value only exists because this screen is open, and nobody else in the world needs to know about it.
Client state
Also calledUI state, local state
State the browser owns outright: which tab is selected, whether the menu is open, what has been typed but not submitted. It is synchronous, never stale, and cheapest kept as close to the component that uses it as possible. Promoting it to a global store 'just in case' is the usual way a codebase acquires a state management problem it did not have.