How do I get feedback on an app without asking clients to install anything?

Share a review link they open in their browser. Tools that support guest commenting — Drafty, Markup.io, Ruttl — let clients leave pinned notes on the live app without creating an account or downloading anything. Avoid sending them into a tool that requires them to join a workspace or install an extension.

How do I get specific feedback on an app design instead of vague responses?

Ask screen-specific questions rather than open-ended ones. "Does the onboarding screen make it clear what the app does before you sign up?" beats "thoughts on onboarding?". Attaching the question to a specific screen — either in a form with a screenshot header or by asking it aloud during a screen share — produces actionable answers instead of impressions.

Can I get feedback on a Figma prototype?

Yes. Share a Figma view-only link with commenting enabled. Clients can comment without a paid Figma account. The limitation: Figma comments are pinned to coordinates in a static frame, not to interactive elements — so if the issue only appears after tapping through a flow, they may not be able to point at it. For interactive state feedback, export the prototype as a live URL and use a review tool instead.

How do I collect app feedback from multiple stakeholders?

Send everyone the same review link rather than separate email threads. A shared link means all comments land in one place, anchored to the same artifact. You see each person's notes without reconciling four sets of annotated screenshots or chasing three separate email chains.

How do I get feedback on a mobile app that isn't live yet?

Share a Figma prototype (view-only with comments on) for early design stages. If it's a built app, use TestFlight (iOS) or an APK share (Android) for native testing — but pair it with a review tool for the UI screens, since TestFlight gives no feedback mechanism beyond verbal or email. If the app runs in a browser (v0, Cursor, web app), a shared review link on the staging URL is the lowest-friction path.

What's the best way to get feedback on a mobile app remotely?

A shared review link on the live or staging URL is the lowest-friction async option — the client opens it on their phone and comments directly on the screen they mean. For complex flows or first-time reviews, combine it with a 30-minute screen share early in the review cycle: the async comments come in sharper after the client has seen the full flow once.

drafty

How to get feedback on an app

Quick answer

To get feedback on an app, share it as a link the client can annotate — a Figma prototype with comments on, a review link on the live URL, or a screen share. Get them pointing at the exact screen and element, not describing it. "The button on the home tab" beats "the blue thing near the top."

Step 1

Share a review link they annotate directly

If you built the app in v0, Cursor, or any tool that produces a URL, paste it into a review tool and send the link. Your client opens it in their browser — on desktop or their phone — clicks the exact button or screen they mean, and leaves a note pinned right there. No account, no install. Tools like Drafty, Markup.io, or BugHerd all support this for live URLs. The difference from sending a screenshot: the comment travels with the context. "The CTA on the pricing screen feels buried" is pinned to that exact spot — not described across three paragraphs you have to decode. This is the lowest-friction option for clients who won't sit on a Zoom call with you.

Step 2

Share a Figma prototype with comments enabled

If the app is still in design and lives as a Figma prototype, share a view-only link with commenting turned on. Clients can leave notes without a paid Figma account — they sign in with Google or create a free viewer account. Figma comments are coordinate-pinned to a frame (not to the underlying element, so they can shift if you reposition things), but for mockups and wires it's the right level of fidelity. One gotcha: Figma comments are pinned to a static frame, not a live interaction — if your client needs to tap through screens to find the issue, they may not be able to reproduce the exact state. For interactive flows, export the prototype as a v0 or web app and use a live-URL review tool instead. Export comments as a CSV at the end of the review so you have a record outside Figma.

Step 3

Walk through it together on a screen share

A 30-minute screen share where you drive and the client reacts out loud beats a week of async email. Share your screen (Zoom or Google Meet), open the app, and click through each screen section by section. The key discipline: let them form an impression before you explain what you were trying to do. Ask "what would you tap first on this screen?" before you point out the primary action. Take notes in a doc as they talk; send it back with timestamped action items after the call. For mobile apps, mirror your phone screen to your Mac (QuickTime + USB or AirPlay) so they're reacting to the real app on a real device — not a browser simulation. This method surfaces flow and interaction issues that a static annotation tool misses.

Step 4

Send screen-by-screen questions, not "what do you think?"

Open-ended questions produce useless answers. Structure your feedback request by screen: Home, Onboarding, Settings — and for each screen, ask one concrete question. "On the onboarding screen, is it clear what happens after you tap Continue?" gets you an answer. "Feedback on onboarding?" gets you "looks good." A short Typeform or Google Form with a screenshot of each screen as a header image works well for clients who won't open a tool. Cap it at six to eight questions — anything longer kills completion. Route responses into a sheet and bring the raw answers to the next call rather than trying to act on them async. One thing most designers get wrong: they ask for feedback on visual polish before the client has used the app. Get flow and clarity feedback first; request visual refinement in round two.

The faster way

If your client keeps saying "the thing on the second tab" — drop your app URL into Drafty and send the review link. They open it on their phone or laptop, tap the exact element they mean, and leave a note pinned right there. No account required. You resolve each comment when it's fixed. Works on v0 apps, Cursor builds, and any public staging URL.

Open a live demo

Questions

How do I get feedback on an app without asking clients to install anything?: Share a review link they open in their browser. Tools that support guest commenting — Drafty, Markup.io, Ruttl — let clients leave pinned notes on the live app without creating an account or downloading anything. Avoid sending them into a tool that requires them to join a workspace or install an extension.
How do I get specific feedback on an app design instead of vague responses?: Ask screen-specific questions rather than open-ended ones. "Does the onboarding screen make it clear what the app does before you sign up?" beats "thoughts on onboarding?". Attaching the question to a specific screen — either in a form with a screenshot header or by asking it aloud during a screen share — produces actionable answers instead of impressions.
Can I get feedback on a Figma prototype?: Yes. Share a Figma view-only link with commenting enabled. Clients can comment without a paid Figma account. The limitation: Figma comments are pinned to coordinates in a static frame, not to interactive elements — so if the issue only appears after tapping through a flow, they may not be able to point at it. For interactive state feedback, export the prototype as a live URL and use a review tool instead.
How do I collect app feedback from multiple stakeholders?: Send everyone the same review link rather than separate email threads. A shared link means all comments land in one place, anchored to the same artifact. You see each person's notes without reconciling four sets of annotated screenshots or chasing three separate email chains.
How do I get feedback on a mobile app that isn't live yet?: Share a Figma prototype (view-only with comments on) for early design stages. If it's a built app, use TestFlight (iOS) or an APK share (Android) for native testing — but pair it with a review tool for the UI screens, since TestFlight gives no feedback mechanism beyond verbal or email. If the app runs in a browser (v0, Cursor, web app), a shared review link on the staging URL is the lowest-friction path.
What's the best way to get feedback on a mobile app remotely?: A shared review link on the live or staging URL is the lowest-friction async option — the client opens it on their phone and comments directly on the screen they mean. For complex flows or first-time reviews, combine it with a 30-minute screen share early in the review cycle: the async comments come in sharper after the client has seen the full flow once.

Keep exploring

How to get feedback on a website How to get feedback on a web design Design feedback tool BugHerd alternative

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