Tech Stacks · Frontend
Redux
Category
Frontend
At the studio
Since 2018
Projects shipped
Numerous
Status
Active
(01) Our take
We use Redux Toolkit when an application has genuine cross-cutting state that multiple disconnected components need to observe. For anything smaller, local state and React Query cover most needs with less ceremony.
Our rule of thumb: if you can't name three different places in the UI that need to read the same piece of state, you don't need Redux yet. The codebases we inherit often have Redux where useState would have done — we're the team that cheerfully rips it out.
(02) What we build with it
Typical work
- Legacy applications where Redux is already the state model
- Apps with genuinely complex shared state (collaborative editors, dashboards)
- Redux-to-lighter-alternatives migrations
(03) How we engage
Engagement shape
Almost always part of a larger frontend engagement rather than a standalone project.
(04) Pairs with
Works well with
Technologies we reach for alongside Redux in most engagements.
Thinking about a Redux project?