The review-loop guides · a straight answer
How to get design feedback without Figma
You have a real page — HTML, or a link — not a mockup in a design tool. You want opinions on it, and the person giving them shouldn't have to learn Figma to help.
Short answer: don't move your work into a design tool to review it — review it where it lives. Send the real page as a link and let people comment directly on it: pinned notes on the live page, a quick screen-share call, or an annotated screenshot for a one-off. Figma is for comping designs that don't exist yet; for a page that already renders, it's a detour that strips the interactivity and taxes your reviewer with an account.
The instinct to "put it in Figma so people can comment" is backwards for built work. Figma comments are excellent — on Figma files. The moment your artifact is live HTML, importing it means screenshotting a thing that already works, losing every hover and tap, and asking your reviewer to sign up. You want the opposite: less friction on their end, and feedback that lands on the actual thing.
Match the method to the situation
There isn't one answer — it depends on how many people, and whether they're looking now or later. Pick your case:
The three no-Figma methods, compared
| Method | Friction for them | Best for |
|---|---|---|
| Pin-on-the-page link | None — open link, tap, type. No account. | Async notes from anyone, especially non-designers on a phone. |
| Live screen-share | Join a call. | One or two people, a fast back-and-forth, reading reactions in real time. |
| Annotated screenshot | They mark up an image. | A single quick "is this button right?" — not iterating. |
Notice the axis that matters isn't fidelity, it's who can participate. The person who catches "this headline doesn't tell me what you do" is often the least technical one in the room. Any method that requires an account or reading code quietly excludes exactly the feedback you most need.
What the pin-on-the-page method looks like
If your page was built by an AI agent, the tightest version keeps the loop inside the build: the agent shares the live page via an MCP tool, you send the link around, people pin notes on the exact elements, and the agent reads them back to apply the ones you approve. No design tool, no export, no login for reviewers — the real page, marked up where the problems actually are. That's what twocents does.