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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM 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

42 sources
Thanks! This kind of thing was lacking for some time, and with the HEEx engine + function components released a couple years ago, we laid the groundwork for extensible component libs, and the community has put out some great options. We list half a dozen in the readme, with https://fluxonui.com/ being the most recent, and fully accessible. There is also one inspired by shadcn https://github.com/phoenixframework/phoenix_live_view?tab=re...
In Phoenix LiveView 1.0.0 is here
gonglexin·Oct 18, 2023Submission

Show HN: Podsee – AI tool for podcast listeners

Hi everyone, I just launched Podsee(https://pods.ee) for podcast listeners, lovers. You can search and listen to podcasts at Podsee. What makes it different is that you can get the AI transcript for an episode. It started as a side project after I resigned my job one year ago. As a programmer, I love Elixir (http://elixir-lang.org/) and Phoenix LiveView(https://github.com/phoenixframework/phoenix_live_view), and want to make a product with it. So I build Podsee. I'm planning to add more AI features to it, like summarize the episode audio, episode to comics, etc. I'd love to invite you all to try out the product and would appreciate hearing your feedback! Thanks!
16 points · Open discussion
Some of the 1.7 stuff has an alert banner that pops up when the connection is broken. I think that could really help. However I haven't put that in our app as I have seen other issues of flakey connection reconnect issues, and I would hate to make any of those more visible with a flashing notice. - https://github.com/phoenixframework/phoenix_live_view/issues... - https://github.com/phoenixframework/phoenix/issues/5102 - https://github.com/phoenixframework/phoenix/pull/5024
In Phoenix 1.7 is View-less
I'm one of the creators of lunatic and it's great to see it on HN again. We have been working on a Rust web framework that builds on top of lunatic, called submillisecond[0]. It's still in alpha and there is a lot to be figured out. Currently, we are attempting to build something like Phoenix LiveView[1] for it. One of the drawbacks of LiveView is that it requires a permanent connection to the backend, but because lunatic uses WebAssembly on the backend we can actually move part of the backend into the browser to allow for low-latency and offline use cases. Hopefully, you will be able to "just write" rust backend apps, but automatically get rich user experiences with offline support. A big struggle for us has been the translation of some of the dynamic patterns from Erlang/Elixir to the strict type system of Rust. Also, Rust can't fully u
Read the rest
nderstand lunatic's processes, because the language was not designed with a concurrency model in mind where each unit of work gets their own heap memory. So there is some de/serialization going on when pushing data between processes. As someone else mentioned, lunatic extends WebAssembly with a concurrency model, networking support, permission system, distributed compute, preemptive scheduling. But it's also a whole system for executing Wasm. So you can from your running wasm app load external .wasm files and spawn processes from them with specific constraints (memory/cpu usage, filesystem access, etc.). Someone in our community is building a system that uses submillisecond in combination with a dynamic router that dispatches workloads to external .wasm files. As you can probably tell, I'm super excited about all the possibilities and the future of lunatic. [0]: https://crates.io/crates/submillisecond [1]: https://github.com/phoenixframework/phoenix_live_view
In Lunatic: Erlang-Inspired Runtime for WebAssembly
If you need any kind of interactivity on the frontend, but are more comfortable with the backend, I would suggest looking at Phoenix LiveView [0] or a similar server-rendered HTML technology for your language of your choice [1]. In short, these solutions take JavaScript out of the mix entirely and basically let you deal with a single logical "app", rather than a separate frontend & backend. [0] https://github.com/phoenixframework/phoenix_live_view [1] https://github.com/dbohdan/liveviews
In Ask HN: What's is your go to toolset for simple front end development?
> I'm not up to date with the less popular web frameworks. Which frameworks do that? One of them is https://github.com/phoenixframework/phoenix_live_view which is a component of Phoenix / Elixir. It will render your initial page over HTTP but then when you transition pages or perform actions using various functions it provides you it will send a diff of what's changed over WebSockets. These actions could be limited to only the 1 user using the site, such as clicking different links in a nav bar to transition between page A and B. The alternative to this is doing what other frameworks like Rails has done with Hotwire Turbo where they make these types of transitions or actions over HTTP. Turbolinks started to do this back in 2015 or whenever it came out and now more recently with Hotwire Turbo there's ways to only update a tiny area of the
Read the rest
page (again over HTTP) but it also optionally supports using WebSockets for when you want to broadcast things to all connected clients, such as updating a counter somewhere or maybe showing a new reply on a blog post, etc.. Laravel has Live Wire and there's also HTMX which is back-end agnostic which all use HTTP for a bulk of their behaviors to send server rendered HTML over the wire. I'm not a Laravel developer but based on their docs they have a drop in solution to handle broadcasting events with WebSockets on demand too[0] so it can continue using HTTP for everything except for when you want to broadcast events similar to Hotwire Turbo in that regard. [0]: https://laravel-livewire.com/docs/2.x/laravel-echo
In Server-sent events, WebSockets, and HTTP
I feel that the simplicity of just building on the server and pushing the updates across the wire is where we are heading. So a lot less double up, with regards needing to write both for the server and client. Validation especially will just need to be written once. Although I do feel Phoenix Liveview is a better option because they implement sockets. Also saw this update today they will allow you to trigger javascript on the client without the sever round trip, it's one of the things people get a bit stuck understanding. Generally they think to pop open a modal or menu requires a round trip to the server but really you should be using Alpine.js or similar for such things. This new pending update remove the requirement of needing a framework like Alpine. https://github.com/phoenixframework/phoenix_live_view/pull/1...
In How Laravel Livewire works

Showing the 15 most recent of 42 sources. Enable JavaScript to search and browse every indexed mention.

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.