An explanation of how to manage global state in Phoenix LiveView compared to JavaScript frameworks like React.
In this episode of Software Sophistication:
- Explaining LiveView.JS why this is required and what problems does it solve?
- Do you need to multiple region deployment in LiveView, and how should it be done?
- How do you handle global state in LiveView in comparison to React and other JS libraries
💻 Pragmatic Studio’s course is the most efficient way to learn Elixir/Phoenix LiveView. Use the course that I use to teach all my apprentices:
➤ Phoenix Liveview Course: pragmaticstudio.com/courses/phoenix-liveview?ref=plicque
➤ Elixir Course: pragmaticstudio.com/courses/elixir?ref=plicque
📝 Have a question about software development? Write a comment and we _will_ answer your question in an upcoming Software Sophistication Q&A show.
🔥 I’ve built an expert team at Or Equals that will revitalize your codebase. Use our experience in Elixir and Phoenix LiveView consulting so you can get back to focusing on the business. Schedule a meeting with me, and let’s chat 👉 OrEquals.com
Preview
Intro
Our Guest: Micah Woods
Micah's views on Elixir
Arpan's Mega LiveView Architecture Comment
What Problems does LiveView.JS Solve?
Multiple Region Deployment in LiveView
How do you handle global state in LiveView?
#liveview #phoenix #elixir #software #softwaredevelopment
Why it's here
1 person recommends this
What people say. Recommended for developers looking to understand state management patterns in Phoenix LiveView compared to React.
Moments people linked to
k
u/kraleppain r/elixir • Recommends
State management in LiveView
Hey everyone 👋
Recently I’ve been exploring the idea of building a state-management solution for LiveView - something loosely inspired by Redux or Zustand from the React world.
The motivation came from patterns I keep seeing both in my own LiveView projects and in projects of colleagues - teams often end up implementing their own ad-hoc ways of sharing state across LiveViews and LiveComponents.
The recurring issues tend to be:
* duplicated or inconsistent state across LV/LC
* the need to manually sync updates via PubSub or `send_update/2`
* prop drilling just to get state deeper into the component tree
These problems show up often enough that many people b…
