Get client feedback on your Rork Web application

Q: What does Rork Web generate?

Rork documents a real Vite and React project that runs in the browser, with routes, components and state available in the editor.

Q: Is the Rork project Preview the live website?

No. Preview is the interactive builder surface. Publishing is a separate step that builds and hosts the app at its rork.app address.

Q: How do Rork Web updates reach the live site?

Project changes remain in Preview until you publish again. Rork shows when an older version is live and provides a Publish latest version action.

Q: What happens when I unpublish a Rork Web app?

Rork takes every address for the project offline immediately but retains the URL so the project can be published again.

Q: Can Rork Web use a custom domain?

Yes after the first publish. Rork can connect a root domain or subdomain, and it issues and renews the SSL certificate. Adding and connecting domains requires an active subscription.

Q: Are Rork iPhone and Android apps reviewed through this page?

No. Rork Web is the browser-first platform. iPhone and Android apps are separate project applications and need a mobile-app review workflow.

Q: Does BugSmash publish or configure Rork Web?

No. Rork continues to control Preview, builds, publishing, domains and backend access. BugSmash records feedback on the accessible published browser app.

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

See how it works

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:

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.
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.
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.
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

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.

Send one BugSmash link

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

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 URL	Review by URL	What to do
Published Rork Web rork.app URL	Works	Paste the visitor-facing address after the publish panel reports the site as Live.
Connected Rork Web custom domain	Works when Live	Use the domain after Rork finishes its certificate, DNS and traffic checks.
Rork project Preview	Builder surface	Use Preview to inspect the project, then publish the intended version for browser URL review.
Project with newer unpublished changes	Older version remains live	Publish again before review when stakeholders need the latest project changes.
Unpublished or offline Rork Web project	Not available	Publish the project again before sharing its visitor-facing address.
Signed-in Rork Web application	Application access required	Use 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.