How to Build and Deploy Your First App with Lovable 2

November 5, 2026

Lovable 2 turns a text prompt into a React and Tailwind app with a Supabase backend, and publishes it to a live URL in under ten minutes. The first version is fast; keeping it maintainable after twenty prompts is where projects stall, so the setup order below matters more than the prompt wording.

I have built three internal tools on it this year, two of which are still in production. The pattern that works is small, specific prompts with one feature each.

How does Lovable 2 differ from a code generator?

It hosts the app, not just the code. You get a preview URL, a git-synced repository, and a Supabase project wired to the frontend. Every prompt edits the running app, and you can roll back to any previous version from the history panel.

The stack is fixed: React with TypeScript, Tailwind, and Supabase for auth, database and storage. You cannot swap in Django or Postgres elsewhere without exporting the code and leaving the hosted workflow.

Pricing: the free plan gives 5 credits a day and non-commercial use. Pro is $25/month with 100 credits, Business around $50 with 100 credits plus custom domains. A simple CRUD screen costs 1 to 3 credits; a full auth flow with email confirmation can cost 8.

What should you do before writing the first prompt?

Decide four things, because changing them later costs credits:

  1. The one job of the app. “Track contract renewals for 12 accounts” beats “a CRM”.
  2. The data model. List your entities and their fields in plain text. If you skip it, the AI invents a schema that fights you for the rest of the project.
  3. Whether login is needed. Email-and-password adds Supabase auth setup and roughly 8 credits.
  4. Who uses it. Internal tools and public apps have different requirements for roles and sharing.

Write those in a note and paste it into your first prompt as context.

What does the first prompt look like?

One screen, one data model, one clear visual instruction.

Build a contract renewal tracker. Table columns: account name, renewal date, owner, annual value, status (active / expiring / lost). Show a list view sorted by renewal date with rows expiring in 30 days highlighted. Use a clean light UI with a left sidebar and no charts yet.

That produces a working list view against mock data. Next prompts add persistence (“move the data into Supabase with a table called renewals and the same columns”), then auth, then the detail view.

Resist asking for the whole app at once. A five-screen prompt produces a five-screen mess that takes six prompts to untangle.

How do you connect Supabase properly?

Use the built-in Supabase integration rather than pasting a connection string. Lovable 2 provisions a project and sets the environment variables for you.

Then enable row-level security on every table and write a policy. Without RLS, Lovable 2 defaults to a permissive policy that is fine for a demo and wrong for anything with customer data. One prompt that works: “Enable RLS on the renewals table so users only see rows where owner_id equals their auth uid.”

What are the realistic limits?

  • Credit burn on redesigns. The AI does not refactor; it rewrites. A “make it look more modern” prompt can consume 6 credits and rewrite components you had already adjusted.
  • Custom server logic. Complex background jobs need Supabase Edge Functions, which the hosted prompt loop does not handle well. Plan to export the repo.

  • Cold starts. Free-plan apps are on a shared environment and can take multiple seconds on first load.

  • Domain and SSL. Custom domains are a paid feature.

When should you export the code?

When two of these are true: you need a backend in another language, you have more than 15 tables, or a human developer is taking over. Exporting early is fine — the repo is standard React and Supabase, and it runs anywhere Node runs.

For an internal tool with two users, staying inside Lovable is cheaper than any alternative I know of.

Quick Summary

  • Lovable 2 generates a React + Tailwind + Supabase app and hosts it on a live URL.
  • Free plan: 5 credits/day, non-commercial. Pro $25/month with 100 credits, Business ~$50.
  • Plan the data model before prompting; changing it later costs credits.
  • Prompt one screen at a time; full-app prompts create rebuild loops.
  • Enable row-level security explicitly — the default policy is permissive.