I built three application archetypes, each implemented twice — once with Context (multiple domain contexts + hooks) and once with Redux Toolkit — with pixel-identical UIs and shared components, so the only variable is the state layer:
- Product catalog — read-heavy, many visible items, selective mutations (add to cart, wishlist)
- Multi-step form — localized updates, validation, dependent fields
- Live dashboard — multiple independent real-time data streams
Performance is measured by render counting: every component reports each render to a tiny registry, and automated benchmarks (Vitest + jsdom) replay identical interactions against both implementations.
Each app also ships with a visible render monitor, so you can watch it live:
A taste of the results: open both, click "Add to Cart" on any product, and watch the render counter — Context re-renders every visible product card; Redux re-renders exactly one. Then try the same comparison in the form app, and the story completely changes. That's the thesis in one sentence: it depends on the application type, and the dependency is measurable.
Where you come in
The benchmarks are half the story — the other half is what developers actually experience and choose. That's a short survey:
29 questions, about 5–7 minutes, fully anonymous — no sign-in, no email, academic use only. If you've built React apps professionally or seriously as a hobby, your answers directly shape the thesis's decision guide.
Questions about the setup? Ask away in the comments.
Top comments (1)
The catalog result is the one you'll want to defend, because "Context re-renders every card, Redux re-renders one" is really monolithic-context vs selector-based store, not Context vs Redux as such. The fair Context version is either split domain contexts with a memoized value and React.memo on the leaves, or useSyncExternalStore with a hand-rolled store and selectors, which is Context-shaped distribution with Redux-shaped selectivity. Having all three in the matrix stops a reviewer saying you handicapped one side. One more measurement note: render count in jsdom is render-function calls, not commits, and a memoized leaf that re-renders to the same output bails before touching the DOM, so the counter overstates the Context case specifically.