When NOT to Use Redux in Your React App

When NOT to Use Redux in Your React App

Redux is powerful, which is why it is overused. Here are the cases where you should not use Redux in your React app.

Small Apps

For small apps with little shared state, Redux is overkill. Local state and Context handle these fine without an extra library and learning curve.

Mostly UI State

If your state is mostly UI flags like modals and dropdowns, that belongs in local component state. Redux is for shared, complex data, not ephemeral UI state.

Form State

Form state is usually local. A form library like React Hook Form is a better fit than Redux for managing field values and validation.

Simple Data Fetching

If you just fetch data in a few components, useEffect or a library like React Query is simpler than wiring it through Redux. Use RTK Query only if you already use Redux for shared state.

When the Team Does Not Know Redux

Introducing Redux to a team unfamiliar with it adds learning overhead. If the app does not need it, the cost outweighs the benefit.

Prop Drilling Is Shallow

If your prop drilling is only one or two levels, it is not a problem. Redux solves deep prop drilling, not shallow passing.

The Takeaway

Do not use Redux for small apps, mostly UI state, form state, simple data fetching, teams unfamiliar with it, or shallow prop drilling. Use it only for genuinely shared, complex state.