What’s Next for Phoenix LiveView? Future Roadmap & JS Integration

Hey everyone! Hope you’re all doing well.

First of all, I want to congratulate the team on the Phoenix LiveView 1.0 release! This is a major milestone for the community, bringing great improvements and making development even more productive. I’ve been migrating parts of my projects to LiveView, and the experience has been fantastic so far.

That got me thinking: what’s next for Phoenix LiveView? Is there an official roadmap, or any planned directions for its future? What new features or improvements can we expect?

Recently, I came across an article from DockYard, where Sergio Arbeo, a senior staff engineer, shared his thoughts on areas where both Elixir and LiveView could improve. One of his points caught my attention:

“Stop the attitude against JS, incorporate a way to send messages between components, add an API to include custom JS commands.”

DockYard Blog: What DockYard Engineers Are Looking Forward to in 2025

I find this perspective interesting. At the end of the day, many of us still need to write JavaScript in our LiveView apps, often relying on hooks, Alpine.js, or even integrations like LiveSvelte and LiveVue. While LiveView’s declarative approach is fantastic, do you think it makes sense to provide more built-in support for JavaScript when needed?

Would love to hear the community’s thoughts on:

• The future of Phoenix LiveView: what’s planned next?
• The balance between LiveView’s declarative model and JS integration.
• Whether there’s room for a more seamless way to handle JavaScript where necessary.

Looking forward to the discussion!