Engineering Note
Hotwire vs React for SaaS apps: what we learned
Hotwire vs React is not a tech choice.
It’s a product decision.
We worked on a SaaS app where frontend complexity was slowing delivery.
React gave flexibility.
But added state, API layers, and coordination overhead.
We tried a different approach.
Used Hotwire for server-driven interactions inside Rails.
Not a full replacement.
Just applied where it made sense.
What we observed:
- Faster feature delivery for CRUD-heavy flows
- Less frontend state to manage
- Reduced API surface between frontend and backend
React still made sense for:
- Highly interactive UI
- Complex client-side state
Hotwire worked better for:
- Business workflows
- Form-heavy interactions
- Speed of iteration
This was not Hotwire vs React.
It was choosing the right complexity for the problem.
Important learning:
Frontend architecture should follow product needs.
Not trends.
It’s a product decision.
We worked on a SaaS app where frontend complexity was slowing delivery.
React gave flexibility.
But added state, API layers, and coordination overhead.
We tried a different approach.
Used Hotwire for server-driven interactions inside Rails.
Not a full replacement.
Just applied where it made sense.
What we observed:
- Faster feature delivery for CRUD-heavy flows
- Less frontend state to manage
- Reduced API surface between frontend and backend
React still made sense for:
- Highly interactive UI
- Complex client-side state
Hotwire worked better for:
- Business workflows
- Form-heavy interactions
- Speed of iteration
This was not Hotwire vs React.
It was choosing the right complexity for the problem.
Important learning:
Frontend architecture should follow product needs.
Not trends.