How do I collect feedback on a Lovable app?

Publish a fixed version somewhere with a comment layer. For one screen, ask Lovable for a self-contained HTML version and paste it into Comma. For the whole app, export the project, run the build, and upload the output folder as a Comma Website — reviewers pin comments to any element on the live pages.

Isn't the Lovable published link enough?

It is enough to show the app. It is not a review tool: there is nowhere to attach a comment to the button that is wrong, and the published app changes every time you publish again, so feedback from Monday may describe a screen that no longer exists on Wednesday.

Does my reviewer need a Lovable or Comma account?

Not for a single-screen review: a published report opens from the link, and you choose whether it is public, password-protected, invite-only or limited to an email domain. Reviewing a full app as a Comma Website means inviting reviewers as commenters, so they sign in once.

Will the Supabase backend work in the review copy?

Only if the reviewed copy can still reach it. A static HTML version has no backend at all, which is usually fine for reviewing layout and copy. A built Website runs in the browser like the original, so client-side calls to Supabase work as long as your project allows the new origin.

Can the agent read the comments?

Yes. Website comments are available over the API and the MCP tool list_website_comments, each with the page path and the element it was left on, so a coding agent can work through the list and mark items resolved.

Share what Lovable built

Lovable gets you from "a booking app for my yoga studio" to something clickable before lunch. The next step — is this right? — involves other people, and that is where a fast build turns into a slow week.

Where the feedback goes wrong

The published app is live and anyone can click through it. What they cannot do is point. So you get:

a screenshot with a red circle, cropped so you can't tell which screen it is;
"the form is confusing" in a DM, with no hint which field;
comments about a version you already replaced, because you published again in the meantime.

Every one of those costs a round-trip before any fixing starts.

Review a single screen

For a landing page or one key screen, the static route is the quickest:

Ask Lovable: "Give me this page as one self-contained HTML file with the Tailwind CDN build and inline JavaScript — no imports."
Paste the result into Comma, or check it first in the free HTML viewer.
Send the link.

Readers select any heading, field label or button and pin a thread to it — commenting on HTML. Scripts run in a sandbox, so tabs and toggles still work; there is no backend behind the copy, which keeps the review on layout and wording.

Review the whole app

When the question is the flow — sign-up to first booking — review the built app:

Connect Lovable to GitHub and pull the project, or download it.
Run npm install && npm run build. Lovable projects are Vite apps, so the output lands in dist/.
Zip dist/ and upload it on the Websites tab in Comma.

Comma hosts the build on an isolated deployment and overlays the anchored comment layer on every page. The upload carries text files only for now, so images need absolute URLs (or to live in your Supabase storage bucket, which Lovable apps often use already). Add the new origin to your Supabase auth redirect URLs if reviewers need to sign in.

Close the loop with the agent

Each Website comment keeps the page path and the element it was left on. Over MCP, list_website_comments returns the full list with that context and set_website_comment_status resolves them, so Claude Code or Cursor can take the review, make the fixes in the exported repo, and tick the comments off. The reviewer sees their thread resolved rather than being asked whether it's done.

Keep it private

A single-screen report can be public, password-protected, invite-only or restricted to your team or email domain — sharing options. A Website starts private; invite reviewers as commenters, or make it public with comments on. Useful when the app is for a client who hasn't announced anything yet.

Try it

Publish your Lovable page →