RAILS LIVEVIEW HOW TO

It has waaay too much code to work around when we’re in “learning” mode, not to mention being critical to the business. 🤓 That involved weeks of research, a bunch of back-of-the-napkin sketches, and experimenting with lots of code. We hunkered down and hammered through it. To answer these and other questions, we did what we always do. How do you incrementally enhance an existing Rails app to take advantage of Hotwire? When do you use one versus the other, and why? What’s the diff between Turbo Drive, Turbo Frames, and Turbo Streams?

RAILS LIVEVIEW HOW TO

And, no surprise, we love pragmatic solutions!īut we were puzzled with how to use Hotwire in practice. It’s is a pragmatic alternative to the complexity of building single-page apps. It lets you dynamically update parts of a page in response to user interactions without writing JavaScript. Conceptually, Hotwire is fairly straightforward. It wasn’t because the fundamental concepts were tricky to understand. And we identified a couple areas that we wanted to “hotwire”.īut we stalled out… Initially Hotwire didn’t “click” for us and that felt frustrating! You may not know that our entire business runs on Rails, and has for the past 15 years. So we started looking at how to use Hotwire in our Rails apps. Hotwire is to Rails what LiveView is to Phoenix. And about the time we were wrapping up that course, Hotwire arrived on the Rails scene. Last year we leaned heavily into Phoenix and created an in-depth (and popular!) LiveView course. They each have their place depending on various project and people factors. You know we’re big fans of both Ruby/Rails and Elixir/Phoenix.

We’re considering cranking up a new course… and we need your help!

Rails liveview