HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
phoenixframework
phoenix_live_view
Elixir2019–2024
phoenixframework / phoenix_live_view

phoenix_live_view

Rich, real-time user experiences with server-rendered HTML

38Distinct people
42Mentions
1Explicit recommenders
6.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Rich, real-time user experiences with server-rendered HTML

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

This article reads to me as more of a "Rails vs Node.js" piece, which seems almost too easy—I would be interested in a more thorough comparison of Rails versus other…

clessg used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:01:40 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year42 dated mentions

Observed mentions: 2019-03-14 20:59:25 UTC to 2024-12-04 04:40:34 UTC.

0510152019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC13112
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC10010
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC505
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC505
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC725
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Phoenix LiveView Phoenix LiveView enables rich, real-time user experiences with server-rendered HTML. Visit the https://livebeats.fly.dev demo to see the kinds of applications you can build, or see a sneak peek below: Phoenix.LiveView.LiveBeats.Demo.mp4 LiveView ships by default in new Phoenix applications. After you install Elixir on your machine, you can create your first LiveView app in two steps: $ mix archive.install hex phx_new $ mix phx.new demo If you have an older existing Phoenix app and you wish to add LiveView, see the previous installation guide. Feature highlights LiveView brings a unified experience to building web applications. You no longer have to split work between client and server, across different toolings, layers, and abstractions. Instead, LiveView enriches the server with a declarative and powerful model while keeping your code closer to your data (and ultimately your source of truth): Declarative rendering: Render HTML on the server over WebSockets with a declarative model, including an optional LongPolling fallback. Rich templating language: Enjoy HEEx: a templating language that supports function components, slots, HTML validation, verified routes, and more. Diffs over the wire: Instead of sending "HTML over the wire", LiveView knows exactly which parts of your templates change, sending minimal diffs over the wire after the initial render, reducing latency and bandwidth usage. The client leverages this information and optimizes the browser with 5-10x faster updates, compared to solutions that replace whole HTML fragments. Live form validation: LiveView supports real-time form validation out of the box. Create rich user interfaces with features like uploads, nested inputs, and specialized recovery. File uploads: Real-time file uploads with progress indicators and image previews. Process your uploads on the fly or submit them to your desired cloud service. Rich integration API: Use the rich integration API to interact with the client, with phx-click, phx-focus, phx-blur, phx-submit, and phx-hook included for cases where you have to write JavaScript. Optimistic updates and transitions: Perform optimistic updates and transitions with JavaScript commands via Phoenix.LiveView.JS. Loose coupling: Reuse more code via stateful components with loosely-coupled templates, state, and event handling — a must for enterprise application development. Live navigation: Enriched links and redirects are just more ways LiveView keeps your app light and performant. Clients load the minimum amount of content needed as users navigate around your app without any compromise in user experience. Latency simulator: Emulate how slow clients will interact with your application with the latency simulator. Robust test suite: Write tests with confidence alongside Phoenix LiveView built-in testing tools. No more running a whole browser alongside your tests. Learning Check our comprehensive docs to get started. The Phoenix framework documentation also keeps a list of community resources, including books, videos, and other materials, and some include LiveView too. Also follow these announcements from the Phoenix team on LiveView for more examples and rationale: LiveBeats: Building a Social Music App With Phoenix LiveView Build a real-time Twitter clone with LiveView Build a real-time Twitch clone with LiveView and Elixir WebRTC Initial announcement Component systems When you create a new Phoenix project, it comes with a minimal component system to power Phoenix generators. In case you want to enrich your developer experience, there are several component systems provided by the community at different stages of development: Bloom: The opinionated, open-source extension to Phoenix Core Components Doggo: Headless UI components for Phoenix Petal Components: Phoenix + Live View HEEX Components PrimerLive: An implementation of GitHub's Primer Design System using Phoenix LiveView SaladUI: Phoenix Liveview component library inspired by shadcn UI Mishka Chelekom: Phoenix + LiveView UI kit and HEEx components Fluxon UI: Elegant and accessible UI components for Phoenix LiveView LiveDebugger LiveDebugger is a debugging tool built specifically for Phoenix LiveView applications. It provides a real-time view into your LiveView processes, making it easier to understand the component hierarchy, inspect assigns, trace lifecycle callbacks, and troubleshoot issues more efficiently. To get started, follow the setup instructions in the LiveDebugger repository. What makes LiveView unique? LiveView is server-centric. You no longer have to worry about managing both client and server to keep things in sync. LiveView automatically updates the client as changes happen on the server. LiveView is first rendered statically as part of regular HTTP requests, which provides quick times for "First Meaningful Paint", in addition to helping search and indexing engines. Then LiveView uses a persistent connection between client and server. This allows LiveView applications to react faster to user events, as there is less work to be done and less data to be sent compared to stateless requests that have to authenticate, decode, load, and encode data on every request. When LiveView was first announced, many developers from different backgrounds got inspired by the potential unlocked by LiveView to build rich, real-time user experiences. We believe LiveView is built on top of a solid foundation that makes LiveView hard to replicate anywhere else: LiveView is built on top of the Elixir programming language and functional programming, which provides a great model for reasoning about your code and how your LiveView changes over time. By building on top of a scalable platform, LiveView scales well vertically (from small to large instances) and horizontally (by adding more instances). This allows you to continue shipping features when more and more
Read the full README on GitHub

What Hacker News says

10 sources
Stimulus Reflex https://docs.stimulusreflex.com/ Laravel Livewire https://laravel-livewire.com/ Phoenix LiveView https://github.com/phoenixframework/phoenix_live_view That's where I see a lot of potential. With Stimulus Reflex I have the convenience and development speed of Rails and I can enhance it with StimulusJS sprinkles and reflexes to create great experiences for the user. The interactivity I get is enough for 90%+ of the webapps out there and the complexity to do it is far less.
In If Not SPAs, What?
If you're interested in seeing a (toy) example project in Nerves, I implemented my own version of an old Finnish reaction speed game [0]. It runs on an RPi0W that I had lying around and has a live score display over WiFi (using Phoenix LiveView [1]). I've still yet to implement a memory game mode, currently it only has the classic speed game (and pro version where you start at score 100, with the corresponding speed). You can find the source on GitLab [2] with the interesting part being in the lib folder. The game folder there contains the game part, while web contains the score UI. It's somewhat messy as I was learning both Nerves and LiveView and just trying out different things. The hardware is still in prototype stage and the LED lights aren't even inside the buttons. I have to say, for me the implementation of the game logic in Elixi
Read the rest
In Nerves – Elixir Platform for IoT
LiveView is a nightmare from a deployment point of view. LiveView stores state on the server associated with the web socket connection. If the web socket connection disappears which is what will happen during a deployment then the user's state will disappear. The value of LiveView is not having to write javascript but the only way to preserve any non-complicated state in LiveView when the web socket disappears is to write javascript. It is only recently that LiveView added support to automatically preserve form input values across a state crash. [https://github.com/phoenixframework/phoenix_live_view/blob/m... | Recovery form input data automatically on disconnects or crash recovery] Prior, to 0.7.0 if the web socket died while you were typing input values in a form then the page would reload and all your input into the form would be wiped
Read the rest
out.
In Lovely Week with Elixir
'JavaScript is a never ending grind' - Wow no better way to summarize it than that. The funny thing is that I've always felt that Javascript the language is pretty straight forward and easy to comprehend. As someone who primarily writes Ruby and really appreciates the functional style of writing code, Javascript lends itself to that style very easily. But the ecosystem around is just that never ending grind. At my last job, over the 3 or so years I was working fully stack, it was just a constant churn. Start with React / Redux / SRR / Jest / Mocha / (probably some other testing frameworks) / Flow. By the end none of the original testing frameworks were being used. React had introduced Hooks, which I actually like, but it was a whole new paradigm to learn again. Flow was out and we needed to migrate to Typescript as quick as possible. And
Read the rest
this is just the React ecosystem! React has its place and I'm definitely comfortable working with it (also writing 0 tests cause I have no idea where to even start for that) but I'm looking forward to the day maybe simple web apps get back to simple setups. Projects like LiveView[0] for Phoenix really give that hope. [0] - https://github.com/phoenixframework/phoenix_live_view
In Ask HN: How to rediscover the joy of programming?
Python is definitely on an undeniable upswing, but you might find your mind more tingly taking a look at Elixir [0] with Phoenix-LiveView [1]. Here's a video that introduces the framework (April 2019): https://www.youtube.com/watch?v=8xJzHq8ru0M It's based on Erlang which has always felt a little rough around the edges, but rock solid and very fast. With Erlang, service boundaries become a thing of the past and tangible state makes debugging a breeze. It's still on the upswing after 20 years in industry. Elixir greatly improves Erlang's tooling and creature comforts and adds syntax that many find more enjoyable. As a guy with web dev PTSD, I've been testing Phoenix and Live-View a bit lately and it really hits a sweet spot between Node's speed and evented nature and the simpler end of React's interactivity. And jobs seem to be appearing
Read the rest
too. Plus Elixir is surprisingly simple to setup[2] so you won't be spending all night fighting Python module dep issues. :) [0] http://elixir-lang.org/ [1] https://github.com/phoenixframework/phoenix_live_view [2] https://elixir-lang.org/install.html
In Ask HN: Which programming languages to learn in 2020 for an experienced dev?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.