// the find
phoenixframework/phoenix_live_view
Rich, real-time user experiences with server-rendered HTML
Phoenix LiveView lets you build real-time, interactive UIs in Elixir by pushing server-rendered HTML diffs over a persistent WebSocket connection, instead of writing a separate JS frontend. It's for Elixir/Phoenix developers who want SPA-like interactivity (live validation, uploads, navigation) without maintaining a JSON API and client-side state management.
The diff-over-the-wire model is real engineering, not marketing: because Elixir data is immutable, the engine can cheaply track which parts of the render tree changed and ship only that, instead of re-rendering whole fragments. LiveViewTest lets you exercise click/submit/upload flows and assert on rendered output without spinning up a browser, which is a genuinely rare and valuable testing story. HEEx (function components, slots, verified routes) and colocated hooks/CSS/JS are a solid, well-thought-out templating layer. The project is actively maintained with a real e2e suite (Playwright) covering dozens of specific regression cases.
You're buying into the BEAM fully — there's no incremental adoption path if your stack isn't already Elixir/Phoenix, and the README doesn't mention that persistent per-connection processes mean horizontal scaling requires sticky sessions or PubSub-based process distribution, which is a real production concern it glosses over. 'No need to write JavaScript' is oversold: anything beyond basic DOM binding (canvas, drag-and-drop, third-party JS widgets) still needs phx-hook and real JS, so the client/server split doesn't fully disappear. The sheer number of numbered issue_XXXX.ex/spec.js regression tests in the e2e suite is a signal this is a mature but still actively-patched system with a long tail of subtle edge cases around morphing, forms, and uploads.