Hotwire plus Ruby on Rails

🚀 Hotwire + Ruby on Rails: The Ultimate Duo for Fast & Reactive Apps (Without JS Overload!) ❤️‍🔥💻

If you’re a Rails developer looking to make your app blazing fast, interactive, and modern — without turning it into a full-blown SPA — Hotwire is your magic wand 🪄. Created by Basecamp (the makers of Rails), Hotwire helps you build real-time, dynamic UIs using HTML over the wire — NOT JSON. That means: less JavaScript, fewer bugs, faster apps. ⚡

🎯 What is Hotwire? (Quick Glimpse)

Hotwire = HTML → Browser via the Cable — Not JavaScript Rendering

🔗 Hotwire is a collection of three parts:

🧠 Why Use Hotwire Instead of React/Vue?

Hotwire lets you:

• Build SPA-like experiences using Rails views
• Skip writing complex JS frameworks 🤯
• Reduce bundle size & faster loading ⚡
• Use Rails for rendering — server side is king 👑

Perfect for: dashboards, chats, notifications, e-commerce carts, live comments, admin panels.

🔥 Ways to Integrate Hotwire in Rails (With Examples)

1️⃣ Basic Hotwire Installation 🛠️

rails new myapp --javascript=importmap --css=tailwind
bin/rails hotwire:install

This installs: ✔ Turbo ✔ Stimulus ✔ WebSocket + Turbo Streams support

2️⃣ Turbo Drive – Make Rails Fast Without Code 🚀

Turbo Drive automatically:

• Intercepts link clicks 🖱️
• Replaces full-page reloads with snappy navigation
• Keeps JS & CSS persistent in memory

Example: A standard Rails link becomes SPA-like

<%= link_to "Products", products_path %>

👉 Loads instantly using Turbo — no config needed!

3️⃣ Turbo Frames — Update Only a Portion of Page 🧩

Turbo Frames let you reload partials instead of entire pages, saving bandwidth & time.

💡 Example — Inline Edit Form ✏️

<!-- show.html.erb -->
<turbo-frame id="user_1">
  <%= render @user %>
</turbo-frame>

<!-- _user.html.erb -->
<p><%= user.name %></p>
<%= link_to "Edit", edit_user_path(user), data: { turbo_frame: "user_1" } %>

➡️ Clicking edit only updates the frame, NOT entire page.

4️⃣ Turbo Streams — Real-Time Updates 📨⚡

Want live comments or orders updating instantly? Turbo Streams use ActionCable + Rails broadcast.

🗣 Example — Live Comments

Model

class Comment < ApplicationRecord
  after_create_commit { broadcast_append_to "comments" }
end

View

<turbo-stream-from "comments"></turbo-stream-from>
<div id="comments"></div>

➡️ Whenever a comment is created — all users see it LIVE 📡

5️⃣ Stimulus.js — Tiny JS for Behavior 🎮

Hotwire still allows small behavior-enhancing JS — but no DOM rendering.

Example — Auto-scrolling chat window

// controllers/scroll_controller.js
import { Controller } from "@hotwired/stimulus"

export default class extends Controller {
  connect() {
    this.element.scrollTop = this.element.scrollHeight
  }
}

<div data-controller="scroll">
  <%= render @messages %>
</div>

6️⃣ Turbo + Forms = No AJAX Required 📝

Form responses update the DOM automatically.

💬 Example — Create Post (Turbo handles response)

<%= form_with model: @post, data: { turbo_frame: "posts" } %>

Controller

def create
  @post = Post.new(post_params)
  if @post.save
    respond_to do |format|
      format.turbo_stream
      format.html { redirect_to posts_path }
    end
  end
end

create.turbo_stream.erb

<turbo-stream action="append" target="posts">
  <%= render @post %>
</turbo-stream>

🏆 Principles for Best Use of Hotwire

🥇 Best Practices to Build Pro-Level Hotwire Apps

✨ Use Broadcasting for dashboards showing live metrics ✨ Cache views using turbo_frame_cache_key ✨ Use StimulusReflex or CableReady for heavy-real-time apps ✨ Build reusable Turbo components → partials + streams ✨ Test Turbo with system tests using Capybara

💼 Real-World Use Cases

🎯 Final Thoughts

Hotwire allows Rails lovers to stay Railsy ❤️, writing fewer files, less JS, faster delivery, and real-time UX that competes with React — with 10% complexity.

If you’re building a product in 2025, this combo is the sweet spot: productivity + performance ⚡