AstonJ
What would you like to see in a future version of Phoenix?
I’m not sure about anyone else, but I’ve been more than content with the promise of Phoenix; a fast, highly scalable and productive (i.e. enjoyable!) web framework. So I haven’t really been thinking about a Phoenix wish-list since it’s already giving me what I wanted.
LiveView changed that! ![]()
So that got me thinking - what else is there that we might love to be in Phoenix - no matter how big of a leap or a dream it might be ![]()
Most Liked
dgmcguire
I see phoenix as feature complete - I’d rather new ideas be tackled in other projects. Even if the aim is to tightly couple some idea with phoenix it would be nice to see stuff namespace’d outside of phoenix so other projects could come along and make X new project pluggable to break off the coupling to phoenix and then Y project could bring X project under its own umbrella of easily integrated tooling
AstonJ
For me, so far Phoenix ticks two of the boxes (speed/scalability, and soon, making front end easier thanks to LiveView) and the only other thing that would make me even more ecstatic is… doing something similar for Mobile! Imagine if we could create native mobile apps (even if just via their web view - like some of the current Mobile frameworks) as easily as what LiveView is going to enable us to do for web apps? How cool would that be? ![]()
Wonder if we all chip in and buy Chris a pack of these each it might actually happen? ![]()
kokolegorille
As a side note there is an Elixir wrapper for gen_statem.








