The "costs" of LiveView

[Exadra37]

@otijhuis

Opening a dialog with LiveView means sending a click event to the server, the server sends data back, then the dialog opens on the client. It’s these kind of roundtrips that are the issue here. In a Vue/React type app you don’t need to go to the server for something like that. This is why you regularly see alpinejs mentioned in combination with LiveView. It can handle certain states on the client without having to do those server calls.

This is using Live View for the wrong thing, and this trend of doing so comes for all that demos for games, and menus, etc… Developers wanting to use Live View for real just got it all wrong from the begin, due to this type of examples.

Only use Live View when you need to perform business logic on some data. When is only about user interaction in the browser NEVER use it.

Sometime ago I replied to another thread with a more detailed answer about this problem of using Live View for the wrong things:

People who have worked in depth with React and SPA's - how realistic is LiveView for a replacement?

In my opinion developers are missing the point about the real use case for Live View, and that is a lot due to disservice that PhoenixPhrenzy contest made and all that useless demos out there, that use live view to build games and change the Dom for pure user interactions with the page that do not require server side business logic. So my take in my product is that I am using Live View but I am keeping it to places where I need to change the data with business logic, aka when a trip to the back…