# Share a Lovable App for Review — Feedback Pinned to the Screen

Canonical: https://commareports.com/agents/share-lovable-output
Published: 2026-09-29

> Lovable publishes an app in one click; collecting feedback on it still happens in screenshots and DMs. How to give reviewers a fixed version with comments pinned to the exact element, and route those comments back to the agent.

# 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:

1. Ask Lovable: _"Give me this page as one self-contained HTML file with
   the Tailwind CDN build and inline JavaScript — no imports."_
2. Paste the result into [Comma](https://commareports.com/new), or check
   it first in the free [HTML viewer](/tools/html-viewer).
3. Send the link.

Readers select any heading, field label or button and pin a thread to it
— [commenting on HTML](/comment-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:

1. Connect Lovable to GitHub and pull the project, or download it.
2. Run `npm install && npm run build`. Lovable projects are Vite apps, so
   the output lands in `dist/`.
3. 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](/docs/sharing).
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 →](https://commareports.com/)**

### Related

- [Share a v0 design for feedback](/agents/share-v0-output)
- [Share a Bolt project for review](/agents/share-bolt-output)
- [Share Replit Agent output](/agents/share-replit-agent-output)
- [Let an agent respond to comments](/agents/let-an-agent-respond-to-comments)
- [Give an agent feedback](/agents/give-an-agent-feedback)