Phoenix LiveView
No written verdict yet. Here is what commenters said.
Why people recommend it
“there was the out-of-the-box live UI with Phoenix/LiveView that was really appealing”
“Super happy to have it incorporated into mainline live view”
Show 3 more
“I like this familly of technologies. Having an SPA-type app that's mostly backend.”
“LiveView is such a breath of fresh air”
“Phoenix LiveView (the inspiration) defaults to using WebSockets because it's much more efficent”
Caveats and dissent
“when I have to do something moderately complicated I have to reach out for a darn js library”
“Livewire, Phoenix LiveView and all the others are a couple levels removed from the browser and you have to suffer the whole indirection chain when something goes wrong.”
Often compared with
From the makers not counted in the ranking
“shipped patches to Ecto, Phoenix LiveView, PostGraphile, and PowerSync”
Threads where it came up
- Phoenix LiveView 1.2 Released 5 mentions
- How we rebuilt Next.js with AI in one week 3 mentions
- Creators of Tailwind laid off 75% of their engineering team 2 mentions
- HTML over WebSockets: real-time SPAs with barely any JavaScript 1 mention
- Ask HN: What are you working on? (August 2026) 1 mention
- LLMs reward expertise 1 mention
Data: phoenix-liveview.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 27
Something else that I think is interesting here is the new HTML streaming APIs in Chrome: https://developer.chrome.com/blog/declarative-partial-updates#out-of-order_streaming These mean that you can for example have a websocket serve just the new HTML, and then let native browser code figure out inserting it into the DOM, without any dependency. I’m guessing things like LiveView could eventually migrate to this if it
“The backend is Elixir, with a Phoenix LiveView dashboard.”
“We use Phoenix / liveview.”
“my Phoenix LiveView template project (which I use for starting new projects)”
“Borrows from Elixir Phoenix's Liveview”
“there was the out-of-the-box live UI with Phoenix/LiveView that was really appealing”
“Ash, LiveView, Tailwind CSS”
“I'll give this a try next time I feel like coding for a hobby.”
“Worth checking out... https://phoenix.new/”
“Super happy to have it incorporated into mainline live view”
“I like this familly of technologies. Having an SPA-type app that's mostly backend.”
“LiveView is such a breath of fresh air”
“There's a guide in the LiveView docs that walks you through the security model.”
“I use it in LiveView all the time”
“Pivot to Elixir Phoenix LiveView is real!”
“Phoenix LiveView dashboard”
“Phoenix LiveView (the inspiration) defaults to using WebSockets because it's much more efficent”
“when I have to do something moderately complicated I have to reach out for a darn js library”
see also: https://dashbit.co/blog/why-elixir-best-language-for-ai
“migrate off of the Next.js and other JS SSR rats nets to Elixir and Phoenix LiveView”
“It’s built entirely with Phoenix LiveView”
“LiveView made the real-time review dashboard easy”
“Livewire, Phoenix LiveView and all the others are a couple levels removed from the browser and you have to suffer the whole indirection chain when something goes wrong.”
I just had a more-detailed look, and I'm not sure where I'd find the pure-HTML stuff? From https://tailwindcss.com/plus/templates/pocket#pricing: "Our website templates are built using Next.js, so all of the markup is written using React" And the individual components that make up these templates don't seem to have pricing attached, nor non-React usage examples?
“I use Phoenix/LiveView for most of my stuff, and it works phenomenally well”
“Building this with Elixir/Phoenix LiveView.”
“We are 100% Elixir and Phoenix LiveView on the backend”