How to share a Lovable prototype for feedback
You built a prototype in Lovable and want people to look at it and tell you what to change. Here are the practical options, including ones that don't involve Ollav.
Option 1: Lovable's own sharing
Lovable can publish your project to a URL, and you can invite collaborators to the project. That's the simplest route when reviewers are already in on the project, or you just need people to click around. Feedback then arrives wherever you ask for it: chat, email, a doc. See Lovable's documentation for current sharing options.
Option 2: a deployed copy on a static host
Export or connect the project to GitHub and deploy it to a static host such as Netlify, Vercel or GitHub Pages. Good if you want a stable public URL. You'll manage deploys and access yourself, and comments still live elsewhere.
Option 3: screenshots and a screen recording
Fast, but people can't point at the exact element, and nobody sees the page behave. Fine for a quick opinion.
Option 4: Ollav, for pinned comments on the real page
Ollav hosts one self-contained HTML file up to 15 MB. A Lovable project is normally a multi-file React app, so first get it into one file:
- Ask the assistant: "Build this as a single self-contained HTML file: inline CSS and JS, images as data URIs, libraries from a CDN." Or build with a single-file plugin; see single-file HTML builds.
- Open https://app.ollav.app and drop the file. You get a link, no deploy.
- Send the link. It's private to your workspace by default and not indexed; invite outside reviewers as guests.
- Reviewers sign in, pin comments on the exact elements and react with emoji, so every note has a name and a place.
- Publish changes as a new version at the same link; earlier comments are kept.
Anything that needs a backend (databases, server routes) won't work: it's static hosting.
Let the agent act on the feedback
Connect Ollav to Claude, ChatGPT, Cursor or Codex (setup). Then ask: "Read the review on my Ollav document, reply to each comment, fix what's fixable, resolve those threads and publish a new version." The agent uses the same link, so reviewers never chase a new URL.