Get client feedback on your Rails application

Q: Should I share bin/rails server with a client?

Not as a durable external review environment. Rails starts that server on localhost in the development environment by default. Deploy the release or intentionally expose a local server through a secure HTTPS tunnel.

Q: Can I review a Turbo-driven Rails interface?

Yes. Review the deployed browser experience and exercise the Turbo navigation, frame updates, and stream-driven states that are part of sign-off.

Q: Why do production assets need to be built first?

Rails' production asset workflow precompiles fingerprinted files for serving. Review after the current styles, scripts, and images have been built and deployed.

Q: Can I review an API-only Rails application?

Review its browser-based client instead. Rails API-only applications skip views, helpers, and assets by default, so the API itself does not provide the rendered page BugSmash annotates.

Q: Does BugSmash depend on a specific Rails host?

No. Use any hosting environment that provides the reviewer with an accessible application URL.

Q: Can reviewers test a signed-in Rails application?

A standard login flow can be reviewed with a permitted test account. For SSO-only or long-lived stateful sessions, use the BugSmash Feedback Widget inside the application.

Q: Do reviewers need server or repository access?

No. They review the deployed browser interface rather than the Ruby project, Rails console, or hosting dashboard.

Paste a browser-accessible Ruby on Rails deployment, send one review link, and collect comments on the routes and interface states your users will actually see. Every note keeps its URL, browser, device and screenshot context.

See how it works

Loved by1,250+Agenciesand companies in 100+ countries

Rails maps requests to application behavior. Review the deployed result.

Rails routes map incoming URLs to controller actions, views render the browser interface, and Turbo can update pages without full reloads. The release environment still determines which assets, data, permissions, and interactions reviewers see.

That makes the deployment itself the source of truth. Four boundaries matter:

The Rails server defaults to development.
Rails documents that bin/rails server starts Puma in the development environment on localhost by default. Use a deployed release configuration for durable external review.
Production assets must match the release.
Rails documents a production asset precompilation step that writes digest-named files for serving. Review after the current CSS, JavaScript, and images have been built and deployed.
Routes, accounts, and data control what reviewers reach.
A browser review can only cover the routes and states exposed by the deployment. Prepare permitted accounts and representative records for the workflows that need approval.
An API-only application has no Rails-rendered page to review.
Rails API-only mode omits browser-oriented middleware and skips views, helpers, and assets by default. Review the separate web or mobile client that consumes the API.

BugSmash adds the review layer around the Rails deployment:

review accessible routes in a real browser, keep comments attached to the rendered element and URL, and preserve approval outside the framework and hosting environment.

How it works

Three steps to a reviewed Rails application

Deploy the release application

Publish the Rails application with its production configuration and current assets, then confirm every route included in review is browser-accessible.

Send one review link

Paste the deployed URL into BugSmash and share the generated link. Reviewers comment on the rendered application without needing repository or server access.

Resolve feedback with its context

Each item carries the URL, selected element, screenshot, browser and device. Assign it, update its status, or send it into the team's delivery tools.

Review the complete Rails experience in the browser

Comment on rendered routes

Attach feedback to the visible interface and URL instead of translating it into route, controller, view, or partial names.

Review responsive layouts

Check desktop, tablet and mobile states from one link and keep the viewport with every comment.

Capture browser context

Browser, device, screenshot and page URL arrive with every report.

Cover Turbo-driven interactions

Review navigation and partial-page updates in the deployed interface rather than relying only on static screenshots.

Exercise authenticated workflows

Use permitted test accounts and representative data so reviewers can reach the forms, validations, dashboards, and permissions that need approval.

Keep release approval

Preserve the review record independently of later Ruby, view, asset, data, or server changes.

Will it work on my Rails application?

BugSmash reviews a browser-accessible Rails frontend. The deployment, routes, assets, authentication, and application permissions still determine what the reviewer can open.

Your URL	Review by URL	What to do
Public Rails production deployment	Works	Paste the public URL and start the review.
Accessible Rails staging environment	Works	Use the staging URL after confirming its assets, routes, permissions, and test data match the release.
Server-rendered or Turbo-driven interface	Works	Review the deployed browser URL and exercise the navigation and interactions included in sign-off.
API-only Rails application	Review the client	Open the browser-based frontend that consumes the API; API-only Rails skips views, helpers, and assets by default.
Local bin/rails server	Not directly	Deploy the application or expose the local server through a secure HTTPS tunnel.
Application behind login or SSO	Access-dependent	Use a permitted test account for a standard login flow, or install the BugSmash Feedback Widget for stateful or SSO-only sessions.

Using the BugSmash Feedback Widget in a Rails application

Add the BugSmash script to the browser-facing Rails interface when reviewers must remain inside authenticated or stateful flows. Install it in the application layout or frontend shell used by the pages under review.