AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Liveview phoenix4/8/2023 ![]() ![]() Interactions as filters, pagination, sorting, etc are very fast to implement with LiveView and it’s pretty fast from the user side too. That’s true but you can make index pages with it even faster and better. You can read the whole article by Chris McCord on this blog post:Ī lot of people would say index pages are so simple you don’t need a hammer as LiveView for it. LiveView fills this gap and challenges what’s possible with server-rendered applications. ![]() ![]() This applies to broad use-cases, including simple real-time updates, client-side style validations with immediate feedback, autocomplete inputs and it can go as far as real-time gaming experiences. There’s a common class of applications where rich experiences are needed, but full single-page applications are otherwise overkill to achieve the bits of required rich interaction. While modern JavaScript tooling enables sophisticated client applications, it often comes at an extreme cost in complexity and maintainability. LiveView powered applications are stateful on the server with bidrectional communication via WebSockets, offering a vastly simplified programming model compared to JavaScript alternatives. Phoenix LiveView is an exciting new library which enables rich, real-time user experiences with server-rendered HTML. Let’s take a description from the first introduction article from December 2018: You can find too many articles about Phoenix LiveView. We implemented our first LiveView page on (merged into the master branch). I can count about 50 LiveView pages in our GitHub account and all of them are already in production right now. We have a lot of experience with this “framework” and we use it almost in every project what we have in Elixir. Our company ( Payout - payment service provider) and our partner companies use it pretty often. ![]()
0 Comments
Read More
Leave a Reply. |