Get client feedback on apps built with Devin Desktop

Q: Can I send a Devin Desktop Preview as the website review URL?

No for external URL review. The official docs describe Preview as a local deployment opened in the IDE or system browser. Deploy the project to a public URL first.

Q: What does App Deploys publish?

The App Deploys beta sends supported websites and JavaScript web apps to Netlify and returns a public windsurf.build URL plus a claim link.

Q: Which frameworks does App Deploys document?

The current docs list Next.js, React, Vue, Svelte, and static HTML, CSS and JavaScript sites.

Q: Can I update an App Deploys site at the same URL?

Yes. Devin Desktop documents redeploying changes to the same URL through App Deploys.

Q: Should I claim an App Deploys project?

The docs recommend claiming important projects. Claiming gives direct provider control, while unclaimed deployments may be deleted after a period.

Q: Can BugSmash review a site deployed somewhere else?

Yes when the separately deployed browser frontend is accessible through a public or supported Basic Auth URL. The hosting provider, not Devin Desktop, controls that deployment.

Q: Does BugSmash change code or deploy from Devin Desktop?

No. Devin Desktop and the selected provider continue to control code, builds and deployment. BugSmash records feedback on the accessible browser result.

Paste the public deployment URL, send one review link, and collect contextual comments on the browser frontend built with Devin Desktop, formerly Windsurf.

See how it works

Loved by1,250+Agenciesand companies in 100+ countries

Devin Desktop can preview and deploy web apps. Those surfaces are not the same.

The current product combines an IDE, local browser previews and an App Deploys beta that sends supported web projects to Netlify.

Four documented boundaries matter before review:

The current name is Devin Desktop.
The official product page says Devin Desktop is the new name for Windsurf, while building on the same IDE foundation.
Preview is a local deployment.
Devin Desktop Previews show a local development server in the IDE or a system browser. A local preview is not a public website URL for external review.
App Deploys is a beta Netlify workflow.
The documented App Deploys beta supports public URLs for Next.js, React, Vue, Svelte and static HTML, CSS and JavaScript projects through Netlify.
Public deployments still need ownership and security decisions.
App Deploys is intended primarily for preview purposes. The docs recommend claiming important deployments, and say unclaimed deployments may be deleted after a period.

BugSmash starts with the deployed browser result:

share the public URL, retain browser context, and leave code, builds, provider settings and application access with the development team.

How it works

Three steps to a reviewed Devin Desktop web app

Deploy the browser frontend

Use App Deploys to create a public windsurf.build URL, claim a Netlify deployment when appropriate, or deploy the web project through another hosting workflow.

Send one BugSmash link

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

Redeploy and verify

Apply the approved code changes, redeploy to the same public URL where supported, and verify the released browser state.

Review the browser frontend built with Devin Desktop

Comment on a public deployment

Attach each note to the rendered interface instead of translating feedback into file names and coordinates.

Review App Deploys output

Use the public windsurf.build URL returned by the documented Netlify deployment workflow.

Cover separately deployed sites

Review a browser frontend hosted outside App Deploys when that deployment is accessible to reviewers.

Check responsive behavior

Review desktop, tablet and mobile presentation while retaining the viewport with each comment.

Capture technical context

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

Keep the workspace private

Reviewers use the deployed app without receiving repository, terminal or Devin Desktop workspace access.

Which Devin Desktop project URL should I review?

Use a public App Deploys URL or another separately deployed browser frontend. A local Preview is not public, and a pasted URL does not bypass authentication or hosting controls.

Your URL	Review by URL	What to do
Public windsurf.build App Deploys URL	Works	Paste the public deployment URL returned by App Deploys.
Claimed Netlify deployment URL	Works	Use the claimed public URL after confirming the intended build is live.
Separately deployed browser frontend	Works when accessible	Use the public or supported Basic Auth URL supplied by the chosen hosting provider.
Devin Desktop local Preview	Local development only	Deploy the project to a public browser URL instead of sharing the local preview.
Unclaimed App Deploys preview	May be temporary	The docs say unclaimed deployments may be deleted. Claim important deployments before relying on them.
Application-login or SSO route	Authentication required	Use the Feedback Widget inside the app after it authenticates the reviewer. A Website-project URL does not bypass sign-in.

Using the Feedback Widget in a Devin Desktop-built app

Add the BugSmash Feedback Widget to the deployed application when feedback must stay inside a logged-in or stateful flow. The application remains responsible for authentication and session state.