Share state across a React app with a store: selectors, actions, slices, and when not to.
Two courses have told you that Context is fine, and they were right. This one is not a reversal. It starts by measuring one specific property of Context that nobody warns you about: it has no selector, so a component that reads a single field out of it wakes up every time any other field changes. You count that yourself, on your own provider, and the number is the reason the rest of the course exists.
Then you build the thing that fixes it. A store is a value that lives outside React with a way to be told when it changes, and it turns out to be a small idea: no provider, no tree to wrap, one hook, and a selector that says which part of the state you actually care about. From there it is actions that live with the state instead of scattered through handlers, slices when one store gets too big, values derived instead of stored twice, and state that survives a reload without lying to you on the first paint.
The last two sections are the ones that make this a course rather than a product tour. You will move state out of the store three times, on purpose: back into a component, back into the URL, and back into Context, because each of those is the right home for something. You finish with Crew State, the board you have carried through five courses, with every piece of its state in the place it belongs and a reason you can defend for each one.
48 Lessons • 50 Practices • 18 Quizzes • 4 Projects · ~10h Total
Not just theory. You finish this course with real work to show.
This is the same in-browser editor every lesson uses. Edit the code, hit Run.
Run code in the browser and see the result immediately. Every lesson works this way.
Stuck? Puff explains the error and nudges you forward, without giving the answer away.
Streaks, diamonds, and certificates. Your progress saves automatically, forever.
Every completed course issues a certificate with a public verification link.
Every certificate has a public verification link employers can check.
One certificate per course. Finish a program and earn its program certificate too.
LinkedIn-ready, with a PDF you can download and attach.
You built the reducer and the context, they worked, and the app has grown. This course gives you the number and then the fix.
You want to know what problem a store solves before you learn one. Section 1 is that problem, measured on code you wrote.
Some of those were right and some were not. Section 8 is a whole section on telling which is which.
React State is free to start, no credit card needed. Some later sections are part of Pro, and finishing every section, including the certificate, needs a Pro plan.
Yes, more than any other prerequisite. Half of this course is a comparison against the reducer-behind-a-context you built there, and section 1 measures that exact pattern. If you have built one somewhere else, that works too.
No. Context is the right tool for what it is for, and this course keeps it in the finished app on purpose. What it does not have is a selector, so every consumer re-renders when any part of the value changes. Section 8 is a whole section on which state belongs in Context and which does not.
Because its surface is small enough that the course spends its time on the concepts rather than on boilerplate, and every one of those concepts transfers to Redux Toolkit unchanged. Redux is still the most common store in existing codebases, and section 8 names it as the one you are most likely to meet at work.
No, and they solve different problems. A store is for state your app owns; React Query is for data a server owns, which needs caching, refetching and staleness. Section 8 says plainly that a store is the wrong home for server data, and React Query is the next course.
Crew State: the team board from the earlier React courses, with its state moved out of React into a store, one selector per component, actions in the store, a filter that survives a reload, a dashboard whose numbers are derived rather than stored, and one piece of configuration deliberately left in Context.
Yes. Finish every item in React State and Devpuff issues a course certificate with a public verification page and an ID you can put on a CV or a LinkedIn profile.
How this course connects to the bigger picture, and what to explore next.
Load, cache, and update server data in React: queries, mutations, invalidation, and optimistic updates.
Start programming for real: variables, strings, decisions, arrays, loops, functions, and objects.
Free to start, no credit card required. Write real code from the first lesson and keep your progress forever.
Start Learning FreeGive your React app real URLs: routes, links, params, nested layouts, and protected pages.