How do I share a Figma prototype without requiring a client account?

Share the prototype link (Play button → Share prototype → 'Anyone with the link'). Viewing needs no account; leaving a comment does. The workaround: export the frames and share via a review tool that allows guest commenting, so feedback doesn't start with a signup screen.

What is the best way to get specific feedback on an app demo?

Anything that lets the client click the exact element. Text feedback ('the button on the second screen') is nearly impossible to act on without a follow-up call. A link where they can pin a note to the spot gives you something you can act on directly.

How do I share an app demo built in v0 or Cursor for client feedback?

Deploy the app to a preview URL (Vercel or the tool's built-in sharing) and send the link. For element-level feedback, also share individual screenshots via a review link — the client can tap through the live URL to understand the flow, then pin specific notes on the static screens. Most clients mix the two: a quick 'looks good overall' after tapping through, then written notes on the three things they want changed.

How do I collect feedback from a client who isn't technical?

Keep the demo in the format closest to a finished product — a live URL or Figma prototype in Presentation mode, not the editor. Remove every login or install step from the feedback path. If commenting requires an account, your first support call is 'why is it asking me to sign up' — which loses the note and the momentum. Guest commenting (click, type, done) is the minimum threshold.

How do I keep feedback organised across multiple rounds of an app demo?

Use a single shared link per review round rather than a new file each time. When notes scatter across email, Slack, and iMessage, it's hard to know which are resolved, which contradict each other, and which screen each refers to. A single link with pinned, threaded comments keeps everything in one place — resolved notes stay visible, open ones carry forward when you push the next version.

drafty

How to share an app demo for feedback

Quick answer

To share an app demo for feedback, export your prototype as a shareable link (Figma, v0, or a live URL), send it to your client, and collect their notes on the specific screen or element. The main gotcha: most tools either require a client account to comment, or the feedback comes back by text with no connection to what they were looking at.

Step 1

Share a Figma prototype link

Open your prototype, hit the Play button to enter Presentation mode, then click Share prototype. Set it to 'Anyone with the link' and copy the URL. Your client gets a click-through flow in their browser — no layers panel, no editor toolbar. One thing most guides skip: viewing is free and requires no account, but leaving a comment requires a free Figma account. For clients comfortable signing up, the built-in comment mode (press C, click the spot) is element-anchored and useful. For clients who aren't — which is most of them — you end up explaining why they're seeing a login screen instead of your design. The export step below is the faster path when that happens.

Step 2

Share a live URL for a coded app or v0 build

If the demo is a coded app — built with v0, Cursor, Bolt, or by hand — deploy it to a preview URL (Vercel, Netlify, or the tool's built-in share button) and send the link. Your client taps through the app as if it were real, on any device. The feedback problem is the same as every other format: the response comes back by text. 'The button on the second screen' is easy to type and almost impossible to act on without a call. A live URL is the right format for flow review; you still need a way to collect pinned notes on specific elements.

Step 3

Export screens and share a review link

Export the screens you want reviewed — PNG for individual states, PDF for a multi-screen flow — and share them via a tool that allows guest commenting. Your client clicks the exact spot and the note pins there. No account, no install. Works across formats: Figma exports, screenshots from Cursor, screen captures from a running app. The trade-off is static images rather than a tappable prototype. For a first visual round ('make the CTA bigger', 'too small on mobile'), static is usually enough.

Step 4

Close the loop: connect notes back to the right screen

Notes by iMessage or Slack — 'the button on the second screen', 'that thing that slides in' — are nearly impossible to act on without a call. Before fixing anything, confirm the screen, the element, and who said it. When feedback arrives by text, ask them to show you on the link. Most clients will, once. If the demo has no one-click comment option, the text path keeps winning because it's faster.

The faster way

If your client keeps texting instead of pointing at the screen, try Drafty. Drop a screenshot, exported PDF, or HTML file, share the link — your client clicks the exact spot to leave a note, no account. When you push a revised screen, the thread stays intact: resolved notes visible, open ones still there. No new link per round.

Open a live demo

Questions

How do I share a Figma prototype without requiring a client account?: Share the prototype link (Play button → Share prototype → 'Anyone with the link'). Viewing needs no account; leaving a comment does. The workaround: export the frames and share via a review tool that allows guest commenting, so feedback doesn't start with a signup screen.
What is the best way to get specific feedback on an app demo?: Anything that lets the client click the exact element. Text feedback ('the button on the second screen') is nearly impossible to act on without a follow-up call. A link where they can pin a note to the spot gives you something you can act on directly.
How do I share an app demo built in v0 or Cursor for client feedback?: Deploy the app to a preview URL (Vercel or the tool's built-in sharing) and send the link. For element-level feedback, also share individual screenshots via a review link — the client can tap through the live URL to understand the flow, then pin specific notes on the static screens. Most clients mix the two: a quick 'looks good overall' after tapping through, then written notes on the three things they want changed.
How do I collect feedback from a client who isn't technical?: Keep the demo in the format closest to a finished product — a live URL or Figma prototype in Presentation mode, not the editor. Remove every login or install step from the feedback path. If commenting requires an account, your first support call is 'why is it asking me to sign up' — which loses the note and the momentum. Guest commenting (click, type, done) is the minimum threshold.
How do I keep feedback organised across multiple rounds of an app demo?: Use a single shared link per review round rather than a new file each time. When notes scatter across email, Slack, and iMessage, it's hard to know which are resolved, which contradict each other, and which screen each refers to. A single link with pinned, threaded comments keeps everything in one place — resolved notes stay visible, open ones carry forward when you push the next version.

Keep exploring

How to share a Figma file for feedback How to share a website for feedback How to annotate a PDF Design feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo