What is Lovable? The AI app builder explained, with a first prompt to try

What is Lovable?

Lovable's documentation describes it as a full-stack AI development platform for building, iterating on and deploying web applications using natural language. You describe what you want. Lovable generates a working application that includes the front end, back end, database, authentication and integrations, backed by editable code. People searching for "Lovable AI" or "Lovable app builder" are looking for this: a tool where the main input is a conversation rather than a code editor.

Four terms come up everywhere in the product, per the docs:

• Account: your personal login, used across every workspace you belong to.
• Workspace: where you and your team work. It holds projects, members, billing and a shared pool of credits.
• Project: one app. It has its own chat, preview, code and version history.
• Chats: conversations outside a project, for thinking through ideas. When something needs building, a chat sends the work to a project.

Lovable is not the only tool of this kind. Bolt, Replit, v0 and others do similar jobs, and the Lovable alternatives page compares them. This page covers what Lovable itself is and how it works.

How does Lovable work?

The editor has two halves. The project chat sits on the left, and a live preview of your app sits on the right. You type what you want, Lovable builds it, and the preview updates. Per the docs, Lovable saves every change as a version automatically, so you can revert, and it can also create drafts, which are separate copies of a project for trying a change without committing to it.

The project chat has three modes, according to Lovable's documentation. Choose by how sure you are about what you want.

Credits are the unit for all of it. Lovable's docs give illustrative Build costs: making a button gray used 0.50 credits, removing a footer 0.90, adding authentication 1.20 and building a landing page with images 2.00. They stress that actual use varies with the scope of the project, and you can see the exact cost of any response in the project chat.

What can you build with Lovable?

Lovable's docs say it supports a broad range of web applications, from early exploration to production systems. They list the following uses.

The docs describe web applications. If your idea is a native iPhone or Android app, check how Lovable's output fits your plan before you commit. The guide to building an iPhone app covers the native route.

A good first project is small, has one user type and one main action. Two examples from the board: what a freelance day actually costs you is one calculator page with no backend, and an RSVP that tells you who is actually coming needs a small database and a shareable link. Browse the board for more, and every idea there comes with a generated build prompt you can paste into Lovable.

What does Lovable generate under the hood?

Real code, in your own repository if you want it there. The docs state that everything Lovable builds is standard code, and you can open it in a code editor inside the project. On the Free plan that editor is read-only. Paid plans can edit the code and download it.

• Framework: per Lovable's ownership page, new apps created from May 13, 2026 use TanStack Start, which runs server code. Older apps use React and Vite and build to static files.
• Backend: Lovable hosts your app and includes a built-in backend, called Cloud, with a database, authentication, storage, realtime and functions. The docs say it uses Supabase's open-source foundation. You can also connect your own Supabase project.
• Hosting: a published app gets an address ending in lovable.app. Custom domains are a paid-plan feature.
• Git sync: you can sync a project with GitHub, GitLab or Bitbucket on every plan. The docs call it two-way sync, so code you change in your repository shows up in Lovable.
• Security scan: publishing runs a Quick scan of the version being published, covering database access rules and dependency vulnerabilities, and a Deep scan reviews your application code for access-control and input problems.

That last point matters for beginners. Code that runs in the browser can be inspected by anyone, so secrets such as API keys must live in the backend's secrets store, not in the front end. Lovable's security best practices page says the same: frontend code should never make security decisions. See the vibe coding security guide for a wider checklist.

How do you start with Lovable?

Lovable's quick start says you can build and publish a first app in about ten minutes, with nothing to install. You can sign up with email, Google, GitHub or Apple, and you can type your prompt on the homepage first and sign up when you submit.

1. Sign up. A personal workspace on the Free plan is created for you.
2. Describe the app. Use the prompt box with Build selected. Write in plain language, in any language.
3. Wait a few minutes for the first version to appear in the preview.
4. Make a change in the chat, then try the app yourself in the preview.
5. Check it works on phone, tablet and desktop sizes, using the preview.
6. Publish to a lovable.app address, or connect a custom domain on a paid plan.

Lovable's own advice for the first prompt is to keep it free of logins and databases. There is less to go wrong, and you can add both later with one prompt. This template follows that advice.

Build a single-page web app for [who it is for] that does one thing: [the one action].

Screen: [what the user sees, in order]
Input: [what the user types or picks]
Output: [what appears after the action]
Use realistic sample data. No login and no database yet.

Done when: [one example input and the exact output you expect].

I want to build [one sentence]. Before you build anything, ask me the five questions you would need answered to build this well. Do not write code yet.

Now add accounts and saving. Users sign in with email, and each user sees only their own [records]. Store [records] with these fields: [field list]. Show me the access rules you are using before you apply them, and explain in two sentences who can read and who can change each record.

Is Lovable free, and what does it cost?

There is a free plan. According to Lovable's subscription plans page, Free gives 5 daily build credits capped at 30 a month, a daily chat allowance, and monthly grants for Cloud and AI usage. On Free, code editing, code download and custom domains are not included, and invite-only publishing is limited to 10 people per project. Paid plans start with Pro, and the docs list Pro at USD 25 a month for 100 credits as of October 2026. Annual billing gives two months free.

Credits are the real limit. The docs say that when a workspace has no credits left, building stops, AI features in deployed apps stop working and apps that use the built-in backend pause. Full plan detail is in the Lovable pricing guide, and the Lovable review covers whether it is worth paying for.

Who is Lovable for, and who should look elsewhere?

For a side-by-side with the two other tools people most often consider, read Claude Code vs Cursor vs Lovable. In short: Lovable is the one where you rarely look at code. Cursor and Claude Code assume you will.

What mistakes do beginners make in Lovable?

• Asking for everything in prompt one. Payments, reminders and a calendar view in the first message gives you a big app that half works. Start with one action.
• Not using Plan mode for big changes. A one-credit plan is cheaper than a wrong build.
• Putting secrets in the front end. Ask Lovable to store keys in secrets and read them only on the server.
• Skipping the access rules. A database without row level rules can expose every user's data. Ask Lovable to explain who can read each table.
• Forgetting the export. Turn on Git sync early so a copy of the code lives in a repository you control.
• Running out of credits mid-build. Watch the cost shown under each response and size your plan to your habits.

If you have an idea but not the time to build it, you can post it on the board instead. Someone else may pick it up, with a build prompt already attached.