Manage application state using Redux, MobX, Zustand, and Context API. Use when centralizing state for complex applications with multiple components.

Frontend State Management Table of Contents [Overview]( overview) [When to Use]( when to use) [Quick Start]( quick start) [Reference Guides]( reference guides) [Best Practices]( best practices) Overview Implement scalable state management solutions using modern patterns and libraries to handle application state, side effects, and data flow across components. When to Use Complex application state Multiple components sharing state Predictable state mutations Time travel debugging needs Server state synchronization Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents [Redux with Redux Toolkit (React)](references/redux with redux toolkit react.md) Redux with Redux Toolkit (React) [Zustand (Lightweight State Management)](references/zustand lightweight state management.md) Zustand (Lightweight State Management) [Context API + useReducer](references/context api usereducer.md) Context API + useReducer [MobX (Observable State)](references/mobx observable state.md) MobX (Observable State) Best Practices ✅ DO Follow established patterns and conventions Write clean, maintainable code Add appropriate documentation Test thoroughly before deploying ❌ DON'T Skip testing or validation Ignore error handling Hard code configuration values

frontend-state-management