With the rise of meta frameworks like Remix and tools like React Server Actions and React Query, do you still need a state management solution like Redux, Mobx or Zustand? Let’s explore this with examples.

React Query has become the standard for server side state management in React applications, however, certain apps still require a lot of client side state. For such apps, there are a lot of great options to handle client side state out there and React Query is not meant to replace any of them. Mobx is one of them and even though it has been out for a while, it has stood the test of time and it is still very powerful.

What if we can combine the power of React Query for server state while keeping the amazing ergonomics and fine-grained reactivity of Mobx for client state?

Meet Mobx Query, a React Query adapter for Mobx that makes this possibility a reality.

The options for front end web development in 2025 are expansive, offering powerful features to consider, like utilising client or server components, and diverse data fetching strategies. Yet, with so many options, it is easy to become overly focused on the architectural approach and risk losing sight of our fundamental goal - user experience. This talk examines the potential downsides of prioritising one architectural approach over another - or prioritising any at all - and poses the question: as we build with these modern frameworks, should the guiding principle be the approach we take, or the quality of the user experience we deliver?

React 19 came out with a lot of new APIs but I still see devs falling back to plain'ol useState and useEffect for everything. Lets explore alternatives.