How to get feedback on a Lovable app
To get feedback on a Lovable app, publish it to a public `.lovable.app` URL and share that link — then pair it with a method that captures where people get stuck, not just what they thought. The built-in URL is enough to share; the missing piece is a way to collect pinned, specific feedback without asking testers to type a wall of text into Slack.
Share the published URL with a review layer on top
Lovable publishes every project to a `yourproject.lovable.app` URL the moment you hit Publish. That link works on any browser, on any device — no account required for the person clicking it. The gap: once your tester opens it, there's no feedback mechanism baked in. The fastest fix is to paste that URL into a tool like Drafty, which wraps it in a review layer — your tester opens the same live app but can click any element and pin a note right there. "The sign-up button is invisible on mobile" lands as a comment anchored to that button, not a three-sentence Slack message you have to decode. Send one link; get back specific, located feedback.
Run a 20-minute recorded session with one person at a time
Async feedback is fast; a live session is diagnostic. Pick one person — a friend, a potential user, someone outside your head — open your Lovable app on a screen share, and ask them to talk out loud as they use it. Your job is to stay quiet. The rule most builders break: they explain the app before the session starts. Don't. Say "take a look at this and try to [do the core thing the app is for]." Watch where they pause, what they click expecting something to happen. Record the call. You'll catch three usability issues in 20 minutes that a week of async feedback wouldn't surface — because users don't report confusion, they just leave.
Send screen-by-screen questions, not "what do you think?"
Vague prompts produce vague answers. Instead of "any feedback on the app?", walk your reviewer through the screens you care about and ask one concrete question per screen. For your onboarding: "After reading this screen, what do you think the app does?" For a core feature: "If you were trying to [accomplish the task], where would you click first?" A short Loom recording of you demoing each screen — with the question as the voiceover — helps reviewers who won't use the app unsupervised. Five to eight targeted questions get you far more than an open request. If you use a form, embed a screenshot of each screen so reviewers know exactly which part you're asking about.
Ask Lovable itself to act as your first tester
Before you hand the app to real users, use Lovable's own AI to surface the obvious gaps. Open your project and prompt: "Act as a first-time user. Walk through the main flow and tell me what's confusing, what you expected to happen but didn't, and what's missing." This is how one builder caught a blank empty-state screen — a "no items yet" page with no call to action — that every real tester would have quietly abandoned. It takes two minutes and surfaces issues a real person wouldn't think to articulate. Code review for the user experience, not a replacement for real testers.
If your testers keep saying "the thing on the left" without pointing at it — paste your Lovable URL into Drafty and send the review link. They open the live app, tap the element they mean, and leave a note pinned to that exact spot. No account, no install. Every comment threads by location so you can resolve them as you push fixes. Works on any public Lovable URL.
Open a live demoQuestions
- Can people comment on my Lovable app without creating an account?
- Lovable has no built-in comment layer for external reviewers. Wrap the published URL in a guest-commenting tool like Drafty — reviewers open the live app and pin notes to specific elements without signing up for anything.
- How do I share a Lovable app for feedback before it's fully built?
- Lovable's preview links (`lovable.dev/preview/…`) are public and view-only for 7 days without requiring login. Share the preview link and pair it with a feedback channel — a shared doc, a form, or a review tool — so testers have somewhere specific to put their notes.
- How do I get useful feedback from non-technical users on a Lovable app?
- Give them a task, not a tour. Instead of "here's the app, let me know what you think," say "try to sign up and [do the core action]." Non-technical users don't know how to give structured feedback — but they navigate honestly. Watch where they hesitate or click the wrong thing. A screen share or a recorded session reveals this faster than any form.
- What's the fastest way to get feedback on a Lovable prototype from potential users?
- Publish the app (one click in Lovable), paste the URL into a message to five people who match your target user, and ask them to try one specific task. Follow up with: "What was confusing?" Not "what did you like?" — that gets compliments. Confusion reports get fixes.
- How do I collect pinned feedback on a specific screen in my Lovable app?
- Lovable's built-in collaboration lets team members annotate the preview inside the editor. For external testers — people who aren't in your Lovable workspace — wrap the published URL in a review tool that supports guest commenting. The reviewer opens your live app, clicks the screen or element they mean, and the note is pinned there.
- Can I get feedback on a Lovable app on mobile?
- Yes. Lovable publishes to a responsive URL that opens in any mobile browser. Share over iMessage or WhatsApp and ask the tester to go through it on their phone. If you add a review tool on top for pinned comments, check it works on mobile too — most do.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.