Stop Using the Flux Pattern for Every Single Blazor App!

Are you building a Blazor app and thinking about using the Flux pattern for state management? Hold that thought. In this video, I break down why the Flux pattern might be overkill for most Blazor apps—and how removing it made my code cleaner, simpler, and even faster (maybe).

I’ll walk you through the real use cases for Flux, where it actually makes sense (thanks Peter Morris!), and where a scoped service or a delegate will do just fine. We’ll compare a Flux-heavy to-do app with a simpler approach, explore alternative libraries like TimeWarp.State, and talk about choosing the right tool for the job.

📌 Demo code from this video is available in my Blazor Deep Dive course on dometrain.com.
🔗 Full course: https://dometrain.com/author/jimmy-engstrom/?ref=jimmy-engstrom
https://github.com/Dometrain/deep-dive-blazor

👇 If you've ever over-engineered a counter app or debated whether Flux belongs in your Blazor toolbox, this one's for you.
Like, comment, and don’t forget to subscribe to Coding After Work!

Sorry about the sound, someone (me) was touching the controls for a live stream.