Phoenix LiveComponents are awesome. That is all.

🇫🇷 LiveComponents Symfony : les limites d'un outil bien fait florent.cc/posts/2026/04/liv…

I’m thinking Mishka’s first simple library (2026) will be a macro, some LiveComponents, and a code generator for automatic form tables & validations in #Ash and LiveView. Hope it comes out clean and gets released. #MyElixirStatus

only thing I really dislike is how Phoenix LiveComponents aren't really great with protocols.

Stop tracking timer references in LiveComponents. Phoenix.LiveView.send_update_after/4 handles delayed component updates automatically - perfect for auto-hide notifications and debounced searches. elixirdrops.net/d/2jPRUep6

And in this case, LiveView integration is purely on the Elixir side. Not on the client. The features we hadn't yet implemented (LiveComponents, Nested LiveViews, etc...) are perfectly do-able. Having to constantly work around the *server* side of LiveView has been the problem.

I just want to add some qualification to the "no production apps" In a few presentations I did say it was production ready as it was passing all LiveView tests with the exception of nested LiveViews, LiveComponents, and some streaming stuff. This all works perfectly fine. We do have a few apps in the App Store but I wouldn't say these are demonstrable examples of "production apps" as I think someone is looking for that SASS product that went all in on LVN.

That depends more on how you want to structure your app with LiveVIew. We currently don't support nested LiveViews, LiveComponents, and some of the more advanced streaming strategies. However, the work that we've been doing since May I'm hoping will finally unlock this for us.

This is built with symfony and LiveComponents 🤯. That means zero JavaScript written and no build system. Amazing how far we’ve come worldbuilder.sylvainblondeau…

This is a gem of tip for when creating truly re-usable LiveComponents! Provide an explicit function to the LiveComponent, rather than an implicit `send/send_update` hexdocs.pm/phoenix_live_view…

This is what's necessary to finally get @LiveViewNative working with nested LiveViews and LiveComponents

Do you have a list of do’s and don’ts for LiveComponents after working on a complex web app?

While working on a complex web app for a client using Phoenix LiveView, we had to deal with many LiveComponents that interacted with each other, and keeping track of all these moving parts was tough. So, we came up with a solution. Meet LiveDebugger 🌳 Link below👇

Nueva revisión del libro Phoenix Framework cubriendo 1.7, Tailwind, LiveView, LiveComponents y mucho más, si ya tenías la primera edición esta te sale gratis: altenwald.com/book/phoenix-f…

Cannot wait! Messenger, UX, LiveComponents, FrankenPHP, DI by Nicolas: every talk is a banger. If you're in the US, this is in your backyard compared to Europe

Introducing LiveDebugger v0.1.0! 📢 Your go-to tool for debugging Phoenix LiveView applications: 🔎Easily inspect assigns of your LiveViews 🔗Trace their callback executions 🌳Dive deep into your LiveComponents tree

Using LiveComponents to Set Flash Messages in Phoenix LiveView elixirmerge.com/p/using-live… via @atimberlake #MyElixirStatus

I know I’m not objective, but LiveComponents are a hidden treasure

Just landed support in @LiveViewNative for LiveComponents, child LiveViews, and our own LiveViewNativeTest suite that mimics Phoenix.LiveViewTest github.com/liveview-native/l… #MyElixirStatus

Live: Hacking on LiveComponents for LiveView Native. Will start around 11:45am EST twitch.tv/bcardarella #MyElixirStatus