phoenixframework/phoenix_live_view

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

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 9th, 2026
Created on September 12th, 2018
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 1,053
Total Stargazers: 6,826 (+0)
Total Subscribers: 164 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Phoenix LiveView is a server-rendered HTML framework that enables rich, real-time user experiences with minimal client-server splitting.

LiveView solves the problem of building interactive web applications without fragmenting logic across client and server codebases. It renders HTML on the server and transmits only the minimal diffs of changed template sections over WebSockets, with a LongPolling fallback. This approach keeps application state and logic centralized on the server while delivering responsive updates to the browser. The framework includes a templating language called HEEx that supports function components, slots, and HTML validation, alongside built-in support for real-time form validation, file uploads with progress tracking, and live navigation that loads only necessary content as users move through the application.

LiveView suits teams building interactive web applications in Elixir who want to avoid splitting concerns between frontend and backend frameworks. It works well for applications requiring real-time updates, complex forms, or file handling, and it ships by default in new Phoenix applications. The tool is particularly valuable for enterprise development where code reuse and maintainability matter, since stateful components with loosely-coupled templates reduce duplication. Developers accustomed to traditional server-side rendering will find the transition natural, while those coming from JavaScript-heavy single-page application frameworks will need to adjust to a server-centric model.

The project maintains active development with regular updates to its core functionality and documentation. The framework receives ongoing refinement to its templating capabilities and integration APIs. Testing infrastructure remains a focus, with built-in tools designed to avoid the overhead of browser-based test suites. The project demonstrates sustained investment in developer experience through comprehensive documentation and example applications.