Publish the app
Publish a snapshot to the generated lovable.app URL or a connected custom domain. Later project changes stay off the live app until you choose Publish changes.
Get client feedback on your published Lovable app
Review the release your visitors will actually use. Paste the lovable.app URL or custom domain, send one link, and collect comments with page, browser, device and screenshot context attached.
Loved by1,250+Agenciesand companies in 100+ countries
Lovable already has comments. Published-app review is a different stage.
Lovable's Project comments and shared preview links are strong tools for feedback while the app is being built. Guests can pin comments on a preview without a Lovable account when comments are enabled.
For client approval on the shipped experience, four differences matter:
Project comments live on the preview.
Lovable anchors Project comments to elements in the project preview. The published app is a separate snapshot at its own URL and only changes when you publish again.
A shared preview link is not a permanent production URL.
Free and Pro preview links expire after 7 days. Business and Enterprise can choose 24 hours, 7 days, 30 days or no automatic expiration, while a published lovable.app URL is the ongoing app address.
Guest comments stop with the preview link.
When a shared preview link expires or is deleted, guest commenting through that link stops. That makes it useful for a review round, but different from a durable approval record tied to the published release.
The native trail stays inside Lovable.
Guest comments notify the project owner in Lovable and collaborators reply from the project. Delivery teams may still need Jira, ClickUp, Slack or a client-facing record that survives project handoff.
BugSmash keeps the published release in the center:How it works
Three steps to a reviewed Lovable app
Send one review link
Paste the published URL into BugSmash and share the resulting link. Reviewers work on the live release without access to the Lovable editor, project chat or source code.
Close the review round
Every comment carries the page, element, browser, device and screenshot. Track status, capture approval, or route the item into the team's task system.
Review the Lovable release, not just the build preview
Comment on the published snapshot
Review the lovable.app URL or custom domain that visitors use, separately from the latest working preview in the editor.
Check every responsive screen
Open the same review at desktop, tablet and mobile sizes and keep each comment tied to its viewport.
Capture browser and device automatically
Every issue arrives with the environment and screenshot needed to reproduce it.
Compare published review rounds
Lovable publishes snapshots only when you choose Publish changes. Keep feedback and approval associated with each reviewed release.
Keep client approval outside the project
Reviewers can sign off without receiving access to the Lovable editor, project chat or source code.
Route feedback to the delivery team
Send actionable comments into the task and communication tools used after the build leaves Lovable.
Will it work on my Lovable app?
Lovable separates the latest working preview from the published snapshot. Choose the URL that matches what you want reviewed.
| Your URL | Review by URL | What to do |
|---|---|---|
| Public app on a lovable.app URL | Works | Paste the published URL and start the review. |
| Public app on a custom domain | Works | Publish the project and wait until the connected domain is live, then paste the domain. |
| Active shared preview link without a password | Works while active | Use it for an in-progress round. Free and Pro links expire after 7 days; published URLs are the better long-term record. |
| Password-protected shared preview link | Works while active | Enter the preview-link password in the review window. Business and Enterprise control its expiration. |
| Workspace or custom-audience published app | Access-dependent | Lovable requires invited viewers to sign in with the permitted email. Use a public review release or the BugSmash Feedback Widget when that access flow blocks URL review. |
| App login using a username and password form | Works | Sign in to a test account inside the review window. Social and SSO-only flows need the BugSmash Feedback Widget. |
Installing the Feedback Widget on a Lovable app
Ask Lovable to add the BugSmash script to the app shell when reviewers need to comment inside a stateful or authenticated flow. Keep Lovable's Project comments for build feedback; use the BugSmash widget for the published experience and the broader approval workflow.
The feedback workflow for teams using Lovable
From preview feedback to published-app sign-off, keep founders, agencies and product teams aligned on the same Lovable release.
Founders shipping products
Collect structured beta feedback on the published app instead of reconstructing the browser, page and device from a message.
See how
Agencies delivering client apps
Move from in-project review to a client approval record tied to the published snapshot and ready for handoff.
See how
Product and growth teams
Review landing pages, responsive states and conversion flows, then route actionable changes into the tools used to ship them.
See howMore platforms
Explore more website feedback workflows
Read the published workflow guide for another website builder, CMS, framework or AI site platform.
- Webflow website feedback guide
- Framer website feedback guide
- WordPress website feedback guide
- Shopify website feedback guide
- Squarespace website feedback guide
- Wix website feedback guide
- Bubble website feedback guide
- Replit website feedback guide
- Claude Artifacts website feedback guide
- Next.js website feedback guide
- React website feedback guide
- WooCommerce website feedback guide
Turn Lovable app feedback into work without losing context
A comment on the published release becomes a task with the URL, selected element, screenshot, browser and device details already included.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
WebhooksThe Lovable app is one deliverable. Review the whole launch together.
Keep the published app beside the pitch deck, product PDF, demo video, launch images, email campaign and mobile build, with every approval in the same project.
Website HTML Widget Video Audio Image PDF PPT Doc Email 3D Model CAD Mobile App - Canvas
Lovable app feedback, answered
Should I review a shared preview link or the published app?
Use a shared preview link for work in progress and the published URL for release approval. Lovable says the preview always shows the latest working version, while the published app is a snapshot that changes only when you publish again.
Does BugSmash work with a lovable.app URL?
Can I review a Lovable custom domain?
Does Lovable already support Project comments?
Do shared preview links expire?
Do reviewers need access to my Lovable project?
Will edits appear on the published app immediately?
Can BugSmash replace Project comments?
Ship Lovable apps without chasing feedback
Paste your published Lovable URL and send the first review link in under a minute.
