This means that, in practical terms, we’re preloading a lot of data. That is, each request comes with a response containing the most information that we are allowed to send and that could be important for a specific page. Using LiveView, I could simply focus on building the web app as a whole without any differentiation between frontend and backend.ĭevelopers typically think about the flow of communication between client and server taking the form of a mail-like conversation. This is largely because LiveView made it easy to build new features, and coding doesn't require switching the context between building the backend in Elixir and frontend in JavaScript. Not only was this an exciting and pleasant task - building an app in Phoenix LiveView was also surprisingly fast. As I familiarised myself with the new paradigm, I found the app building process to be refreshing, as it presented me with a completely different approach to building certain features.
This was an exciting task for me, as it was my first contact with LiveView.
ELIXIR PHOENIX LIVEVIEW HOW TO
This isn't a step-by-step tutorial on how to create a web app in LiveView, and each person who uses the program for similar tasks will undoubtedly take an individual approach to how they work. Please note that in this post, I’ll be describing my personal experiences and chosen approaches while using Phoenix LiveView. I did so without writing any JavaScript code (if we can exclude initialising date pickers on some inputs!). At the start of this year, I had the pleasure and opportunity of building an entire application using Phoenix LiveView.
0 kommentar(er)
