Analysis updated 2026-07-09 · repo last pushed 2024-03-27
Build a live chat where messages appear instantly without writing JavaScript.
Create a real-time dashboard that updates as data changes on the server.
Make an interactive search box that updates results as the user types.
Build a live notification feed that pushes updates to the browser automatically.
| davidpdrsn/axum-live-view | azw413/ternos | qewer33/ratscad | |
|---|---|---|---|
| Stars | 214 | 103 | 98 |
| Language | Rust | Rust | Rust |
| Last pushed | 2024-03-27 | 2026-03-19 | — |
| Maintenance | Dormant | Maintained | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 4/5 | 3/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Rust and familiarity with the axum web framework, the project is experimental and APIs may change.
axum-live-view lets you build interactive, real-time web interfaces without writing any JavaScript. Instead of sending a static page and then layering on client-side code to make things interactive, your server keeps a live connection open with each user's browser and updates the page as things change. Think of it as a way to build something like a live chat, a real-time dashboard, or an interactive form without touching frontend JavaScript at all. Here is how it works under the hood. When a user first visits your page, the server sends back fully rendered HTML, which is good for search engines and fast load times. Then a small piece of built-in JavaScript connects back to the server over a persistent connection called a WebSocket. From that point on, when a user clicks a button or types in a field, that event goes straight to your server-side code. Your code decides what happens, re-renders the relevant HTML, and sends only the changed pieces back to the browser. The browser applies just those small updates, keeping everything feeling snappy. If the connection drops, the client automatically reconnects and starts fresh. This is useful for developers who want to build rich, app-like experiences but prefer to keep all their logic in a single backend codebase rather than splitting work across a frontend and backend. For example, if you are building a counter that increments when clicked, a search box that updates results as you type, or a notification feed that updates live, this approach handles it cleanly. You define your interface as a template with dynamic values, wire up what happens on click events, and the framework takes care of the communication layer. The project is explicitly marked as a work in progress, and the author warns that everything is subject to change and it should not be used for anything serious yet. It is essentially an experiment bringing a popular pattern from the Elixir and Phoenix framework world into Rust.
Build interactive real-time web apps without JavaScript. Your Rust server stays connected to the browser and pushes live updates.
Mainly Rust. The stack also includes Rust, axum, WebSockets.
Dormant — no commits in 2+ years (last push 2024-03-27).
No license information provided in the explanation.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.