# Share a Lovable app with a client, and see what they did

- URL: https://getroomi.com/share/lovable
- Sources checked: 12 October 2026
- Built: 2026-10-13

You built it with Lovable. Now show a client, and see what they did. Roomi gives each client a link of their own, with nothing to sign up for, and shows you every visit, click and minute.

## What sharing from Lovable gives you today

Each line about Lovable is from its maker’s own pages, read on 12 October 2026. Each source is listed at the foot of the page.

|  | Lovable | Roomi (ours) |
|---|---|---|
| Opens for a client without an account | Partly: On Lovable’s Free and Pro plans, a published app is open to anyone with its address by default; “Invite only” limits it to people you add, who must log in. | Yes: They open their link and they’re in, with nothing to sign up for. |
| Who looked, and what each did | Partly: Lovable’s project analytics show visits, page views, sources and devices for a published app. They count visits, not people, and signing in to the app does not link visits to one account. | Yes: Each person by name: every visit, click and minute, how far they took the tour, and who they passed it to. |
| Apps that need a server | Yes: Since 13 May 2026, new Lovable projects are rendered on a server, built on TanStack Start. Earlier ones were single-page apps deployed as static files. | Yes: A demo with a server runs as a container on Pro and up, with a copy of its own for each viewer. |

Lovable and Roomi, side by side. What Lovable does is from its own pages, read on 12 October 2026. Roomi is ours.

What the marks mean: “Partly” means partly, or with conditions; “Not listed” means not on their own pages.

## The Roomi way, from your Lovable project’s code

Six commands, run by you or by your coding agent. Nothing goes live until you commit.

1. **Describe the demo, then rehearse it** — Work in the folder that holds your Lovable project’s code, on your own computer, with its live backend swapped for sample data. The CLI’s first command describes the demo and leaves a guide written for your coding agent, so Claude Code or Cursor can run the rest. Deploy rehearses: it builds, checks for secrets and shows what would go live. Nothing has left your computer.
2. **Put it live** — Deploy again with commit, and the room is live. A new build can go to a preview first, for you to check before any viewer sees it. If a change goes wrong, roll back to the last good build. Each build keeps its log, for when one fails.
3. **Make a link for each person** — On Pro, make a private link for each client, with their name on it. Send it yourself, by email or however you usually reach them. Roomi sends nothing. When you send it, tell them who you are and that Roomi records what they do in the room for you. Our terms ask you to.
4. **See who looked, and what held them** — Each person’s visits in order, the screens they stayed on, how far they took the tour, and who they passed it to.
5. **Follow up while they’re still thinking about you** — Each viewer answers “What happens next?”: a meeting, a yes, later, a colleague, a question, or not for them. Roomi ranks who to call first. Ask your own Claude to draft a follow-up from what they did. Nothing is sent until you send it.

```text
$ npm install -g @getroomi/cli
$ roomi login
$ roomi init
$ roomi deploy
$ roomi deploy --commit
$ roomi link "Priya Shah"
```

## Ways to share a Lovable app with a client, ranked

Ranked for one job: a client trying the real thing, and you knowing what they did. Roomi is ours.

1. **Roomi** (ours) — your own build, running, at a private link for each person, with nothing to sign up for. You see every visit, click and minute, by name.
2. **Lovable’s own published link** — On Lovable’s Free and Pro plans, a published app is open to anyone with its address by default; “Invite only” limits it to people you add, who must log in.
3. **A screen recording** — easy to send, but they watch you use it rather than try it. Loom names a viewer only when they watch while logged in to Loom. Anyone else shows as an anonymous view.
4. **Screenshots in a deck** — no setup at all, and nothing to click. A deck tells you, at best, that it was opened.

## Questions

### Can a client open my Lovable app without an account?

On Lovable’s Free and Pro plans, a published app is open to anyone with its address by default; “Invite only” limits it to people you add, who must log in. A Roomi link opens for the person it was made for, with nothing to sign up for.

### Does Lovable show me who opened my app?

Lovable’s project analytics show visits, page views, sources and devices for a published app. They count visits, not people, and signing in to the app does not link visits to one account. Roomi records each person by name: their visits in order, the screens they stayed on, and who they passed it to.

### Will my Lovable app run on Roomi?

Since 13 May 2026, new Lovable projects are rendered on a server, built on TanStack Start. Earlier ones were single-page apps deployed as static files. One with a server runs on Roomi as a container demo, on Pro or above, with its live backend swapped for sample data. One built as static files runs on any plan.

### Does my client need a Roomi account?

No. Their link takes them straight into the room, with nothing to sign up for. The link is their key, and it carries their name.

### What does Roomi cost?

Free costs nothing: static demos, listed on the community at one public address, with total views. A private link per person and everything each person did start on Pro, at £4 a month or £40 a year, before VAT.

### Do I have to tell a client their visit is recorded?

Yes. Before or when you send the link, tell each viewer who you are and how to reach you about their data. Tell them too that Roomi records what they do in the room and shows it to you. Our terms ask for both.

## Fair, and dated

Every claim about another product on this page is from that product’s own pages, each read on the day beside it, the oldest on 12 October 2026. Roomi is ours, and says so. If something here is out of date, tell us and we’ll fix it the same week.

- Lovable, read 12 October 2026: [docs.lovable.dev/features/publish](https://docs.lovable.dev/features/publish)
- Loom, read 12 October 2026: [support.atlassian.com/loom/docs/see-who-has-viewed-your-video/](https://support.atlassian.com/loom/docs/see-who-has-viewed-your-video/)
- Lovable, read 12 October 2026: [docs.lovable.dev/features/analytics](https://docs.lovable.dev/features/analytics)
- Lovable, read 12 October 2026: [lovable.dev/blog/building-apps-using-tanstack-start](https://lovable.dev/blog/building-apps-using-tanstack-start)

## Read more

Guides that go further into the same question.

- [How do you swap real data for mock data in a demo built with AI?](https://getroomi.com/guides/how-to-use-mock-data-in-an-ai-built-demo): Four ways to give an AI-built demo its own data, and how to ask your AI agent for each. Make it look like the client’s world, with nothing real in it.
- [Is it safe to send a client a link to an app you built with AI? A checklist](https://getroomi.com/guides/is-it-safe-to-send-a-client-an-ai-built-app): Eleven checks before an app built with Claude, Lovable or Bolt goes to a client: data, keys, backends, links, and what to tell them.

## Give each client a link of their own

Put your Lovable app in a room, send it, and see who leaned in.

[Get started free](https://app.getroomi.com/start)