BlackFriday

50% offon all annual plans

00d00h00m00s
Explore plans
Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Rork logo

Get client feedback on your Rork Web application

Paste the published rork.app or connected custom-domain URL, send one review link, and collect contextual comments on the browser experience.

https://

This workflow covers Rork Web projects that run in a browser. Rork’s iPhone and Android apps are separate application surfaces.

Knauf
Radancy
Frontier
City of Boroondara
Berlin Heart
GVBOCES
Bville
Frost Collective
Mediapilote
Medwiki
Musaffa
Sharp Guys Web Design

Loved by1,250+Agenciesand companies in 100+ countries

Rork Web previews and publishes a browser app. Native apps remain separate.

Rork Web generates Vite and React code, previews it beside the project chat, and publishes it to a Rork-hosted address or connected domain.

Four documented boundaries matter before review:

  1. Rork Web is the browser product.

    Rork Web creates a Vite and React project that runs in the browser and publishes to an address on rork.app. It is distinct from the iPhone and Android platforms.

  2. Project Preview is not the published site.

    The interactive project Preview supports Desktop, Tablet and Phone widths. Publishing is a separate action that makes the web app live at its visitor URL.

  3. Changes stay in Preview until published again.

    After the first release, Rork marks the live site as an older version when the project changes. Publish again to update it; unpublish takes every site address offline without deleting the URL.

  4. Custom domains follow the first publish.

    Rork enables custom-domain connection after the project is first published. An active subscription is required, and Rork issues and renews the SSL certificate.

BugSmash keeps review on the published browser result:
share the live URL, retain page and device context, and leave Rork publishing, domains, backend access and mobile apps unchanged.

How it works

Three steps to a reviewed Rork Web release

1

Publish the web project

Choose the Rork Web platform, verify the project Preview, then publish it to the assigned rork.app address or connect a custom domain after the first publish.

2

Send one BugSmash link

Paste the accessible published URL into BugSmash and share the generated review link with clients or QA.

3

Publish again and verify

Apply approved changes in Rork, publish the latest version, and verify the live browser app and domain state.

Review the published Rork Web experience

Comment on the live web app

Attach feedback to the page and interface location the browser user is actually navigating.

Review the rork.app release

Use the published Rork-hosted visitor address for browser review.

Cover connected domains

Review a root domain or subdomain after Rork reports its certificate, DNS and traffic states as live.

Check responsive behavior

Review desktop, tablet and phone layouts while retaining the viewport with each comment.

Capture technical context

Keep the page URL, browser, operating system, viewport and screenshot with each application comment.

Keep mobile releases separate

Use a separate mobile-app workflow for Rork iPhone or Android builds rather than treating a simulator or store listing as a website URL.

Which Rork URL should I review?

Use the published rork.app address or a connected custom domain for Rork Web. The project Preview, offline state and native apps are separate, and a pasted URL does not bypass sign-in.

Your URLReview by URLWhat to do
Published Rork Web rork.app URL WorksPaste the visitor-facing address after the publish panel reports the site as Live.
Connected Rork Web custom domain Works when LiveUse the domain after Rork finishes its certificate, DNS and traffic checks.
Rork project Preview Builder surfaceUse Preview to inspect the project, then publish the intended version for browser URL review.
Project with newer unpublished changes Older version remains livePublish again before review when stakeholders need the latest project changes.
Unpublished or offline Rork Web project Not availablePublish the project again before sharing its visitor-facing address.
Signed-in Rork Web application Application access requiredUse the Feedback Widget after the app authenticates the reviewer. A Website-project URL does not bypass sign-in.

Using the Feedback Widget on a Rork Web app

Add the BugSmash Feedback Widget when review must remain inside a signed-in, personalized or stateful Rork Web experience. The application and Rork Cloud continue to control accounts and data access.

Turn Rork Web feedback into trackable work

Route an actionable browser comment with its page URL, selected location, screenshot, browser, operating system and viewport context preserved.

Context stays attached from comment to completion.

Send to your workflow

The destination changes. The context does not.

Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks

The Rork Web app is one deliverable. Review the complete release together.

Keep the web app beside screenshots, PDFs, videos and launch materials, with feedback and approval in one project.

  • Website
  • HTML
  • Widget
  • Video
  • Audio
  • Image
  • PDF
  • PPT
  • Doc
  • Email
  • 3D Model
  • CAD
  • Mobile App
  • Canvas

Rork Web feedback, answered

Which Rork URL should I send for website review?

Use the published Rork Web address on rork.app or a connected custom domain after it reports a Live status.

Ship Rork Web applications without chasing feedback

Paste an accessible published rork.app or custom-domain URL and send a focused review link.

BugSmash website review interface with comment controls