Collecting Feedback on a Lovable Project: Your Options
How Lovable's built-in comments work, and where a dedicated feedback layer fits in
Lovable is genuinely great. You type a sentence, it builds an app, and one click puts it live on a real URL with SSL and a CDN and all the infrastructure words that normally require a person named DevOps Greg. For a lot of people, that's the entire toolbox. No notes.
It even has commenting built in. Which raises a reasonable question: do you need anything else to collect feedback? Sometimes no. Sometimes yes. Let's go through it without anyone getting hurt.
How commenting works in Lovable
Pretty nicely, actually. Guest comments are on by default, so anyone with your preview link can leave a note without making a Lovable account, a small mercy, given that the average human now maintains roughly 4,000 logins. Comments land, the owner gets notified, the team replies from the editor. For a quick round of "hey does this look okay," it's about as frictionless as it gets.
That's Lovable's whole personality: build, publish, share, all in one place. When your work lives entirely inside Lovable, its built-in comments fit like they were supposed to. Because they were.
Where a dedicated feedback layer sneaks in
A few situations wander just outside what built-in preview comments are built for. These aren't Lovable's failings, every feature has an edge, and this is simply where this one ends. No villains in this story.
When feedback needs to outlive a week
Lovable's preview links are temporary, they expire after about seven days, and the comments clock out with them. Great for a quick look. Less great if your review cycle has the lifespan of an actual project, which tends to be "longer than a week and full of people who reply on day nine." dot. links don't expire. They just... stay. Like a good houseplant.
When the thing you're reviewing is already published
In Lovable, comments live on the preview. Publishing is a separate step that ships your app to its permanent URL. So the moment your work is live on your real domain — frequently the exact moment you want a client or stakeholder to bless it, you've left the comment-able preview behind. dot. works on any live URL, so the version people are actually staring at is the version they can mark up.
When you build in more than one tool
Many teams use Lovable and Claude and v0 and something a developer hand-wrote at 2 a.m. Built-in comments live inside the tool that made them, so feedback scatters across platforms like socks across a dryer. dot. sits on top of all of them, one dashboard, every project, including the Lovable builds you've pushed live.
When a comment needs to bring context
dot. clips a snapshot of exactly what the reviewer was looking at onto every comment, plus their browser, OS, and screen size. So "this looks broken on my end" arrives with evidence instead of vibes, and you can see their end without launching a forensic investigation.
The part that connects to how you build
One more thing, specific to AI-built projects, and honestly the fun part. dot. plugs into AI tools through MCP, which means feedback can travel back into whatever built the project. Tell Claude to pull your dot. feedback and fix what reviewers flagged, and it reads each pinned comment, snapshot and context and all, then regenerates the build with the changes made. Your reviewers, essentially, talking directly to the robot. Everyone's polite about it.
Lovable has its own version of this loop inside its agent, and it's good at it for Lovable projects. dot. just spreads the same trick across whatever tools you happen to use.
So which should you use?
Plot twist: usually both.
Use Lovable's built-in comments when you're building in Lovable, sharing a quick preview, and everyone's looking at that preview this week. Fastest path, already there, zero setup.
Reach for dot. when feedback needs to outlast a seven-day link, when the work's gone live on a real domain, when you're building across several tools and want one tidy pile instead of six messy ones, or when you want comments that carry context and boomerang back into your AI as fixes.
Lovable takes you from idea to live app at a speed that feels vaguely illegal. dot. makes sure the feedback on that app, wherever it ends up living, is easy to collect, keeps its context, and turns into actual changes. Two tools, same team. No rivalry, no dramatic music.
Building in Lovable, Claude, v0, or somewhere else entirely? dot. gives you a link where anyone can pin feedback - no account, no expiration, no forensic investigation. Get started free