Phoenix LiveView 1.0.0 is here

Original Article ↗ Hacker News Discussion ↗

Overall reception & developer experience

  • Many commenters describe LiveView as “magical,” joyful, and a major productivity boost, especially for solo or small teams.
  • Backend-focused developers report it gave them confidence to build rich UIs without much JavaScript.
  • Several say Elixir + Phoenix + LiveView has been the best professional decision they’ve made and enabled them to ship multiple production apps and startups.

Tradeoffs vs JS/SPAs and ecosystem

  • Pros: unified stack, far less JS, easy real-time features, strong DX; avoids coordination cost between separate front-end/back-end teams.
  • Cons: much smaller ecosystem than React/JS; fewer ready-made widgets (modals, WYSIWYG editors, layout systems), so some patterns must be built from scratch.
  • Interop with JS libraries (e.g., ProseMirror-like editors, ag-grid, maps, charts) is reported as straightforward via LiveView hooks.

Connectivity, offline behavior, and networking

  • LiveView relies on a semi-reliable connection (WebSocket or long-poll fallback). Some report it degrades better than expected; others highlight the “elevator problem” where apps feel unusable on flaky mobile connections.
  • Offline-first behavior is mostly absent at the framework level but explored via CRDTs, PWAs, and local-first sync tools; some see this as the main remaining weakness.

Performance, scalability, and async workflows

  • Commenters emphasize BEAM/Elixir strengths: lightweight processes, concurrency, and ease of server-initiated updates.
  • LiveView encourages async workflows instead of blocking UIs on long-running tasks, making progress updates and notifications easy.

UI components, design, and demos

  • There is demand for polished, accessible component libraries comparable to major JS ecosystems.
  • Several community component systems and Tailwind-based libraries are mentioned, but some still see room for a “shadcn-level” design system.
  • Requests for official demos include: optimistic UIs (drag-and-drop, Trello-style), advanced pagination/virtualization, rich charting dashboards, and complex tables.

Tooling, installation, and v1.0 status

  • A new one-command installer for Phoenix/LiveView is highlighted; some friction exists on certain distros, with suggestions to use version managers.
  • The changelog and existing docs are referenced for detailed 1.0 changes.
  • LiveView is considered stable; some are updating long-lived production apps now that 1.0 is out.

Architecture, data handling, and pagination

  • Commenters praise context separation, Ecto-based validation, and the ease of later exposing APIs alongside LiveView.
  • Discussion covers pagination strategies (offset vs cursor), URL size limits, and libraries for cursor-based pagination, including past security concerns and ensuing fixes.
  • Streams are highlighted as a way to handle large, virtually infinite lists without keeping full collections in memory.

Mobile, native, and other ecosystems

  • Interest in LiveView for mobile is high. Efforts like LiveView Native and Elixir-in-app runtimes are mentioned, but Android support has seen setbacks.
  • Comparisons arise with Blazor, Vaadin, htmx, Replicache-like models, and Gleam-based approaches; no consensus winner, but LiveView is seen as distinctive in leveraging the BEAM.

Careers, adoption, and hosting

  • Some developers report full-time work in Elixir and ease of hiring; others ask about remote/pay levels, indicating curiosity but some uncertainty about market size.
  • Hosting questions surface (vs Cloudflare/JS stacks), but no clear canonical answer emerges in the thread.