Lovable glossary
40 terms you'll meet while building with Lovable, explained without jargon. If a word in a guide or answer trips you up, it's probably defined here.
Jump to a group
Lovable basics
- Build error
- A failure that stops your app compiling, usually from a missing file, a bad import or broken syntax. Paste the exact message when asking for a fix. Learn more
- Console error
- A runtime problem reported by the browser while the page is open. It means the app built but something failed in use. Learn more
- Credits
- The usage unit Lovable spends when it works on your project. Bigger, vaguer requests burn more credits than small, specific ones. Learn more
- GitHub repository
- A synced copy of your project's code you own outright, useful for backups, code review and working with a developer. Learn more
- Lovable
- An AI app builder where you describe what you want in plain English and it writes and runs a real React web app for you, editable at any time. Learn more
- Preview
- The live copy of your app that updates as you build. It is private to your project and separate from the published site.
- Version history / revert
- The saved timeline of your project. Reverting rolls the code back to an earlier working point when a change goes wrong.
Prompting
- Context (project knowledge)
- The background Lovable carries into every prompt — your goals, rules and conventions. Good context stops it re-deciding things you already settled. Learn more
- Hallucination
- When an AI invents something plausible but untrue — a setting, a function, a file. Verify anything load-bearing before you rely on it.
- Iteration
- Improving a build in small, checkable steps rather than one giant request, so you can tell exactly which change broke something. Learn more
- Prompt
- The instruction you give Lovable. A good prompt states the goal, the screen or file it affects, and the rules that must not change. Learn more
Data & backend
- API
- A defined way for two systems to talk. Your app calls an API to fetch weather, take a payment or send an email. Learn more
- Database
- Where your app stores information that must survive a refresh: users, orders, posts, form submissions. Organised into tables. Learn more
- Lovable Cloud
- The managed backend Lovable turns on for you — database, authentication, file storage and server logic — so you never wire up a separate provider. Learn more
- Server function
- Code that runs on the server instead of in the browser, used for anything a visitor must not see or tamper with.
- Table
- One kind of record in your database, like a spreadsheet: columns define the fields, rows hold each entry. Learn more
- Webhook
- A URL in your app that an outside service calls when something happens — a payment succeeding, an email bouncing. Always verify the caller. Learn more
Accounts & security
- Authentication
- Proving who a visitor is — email and password, a magic link, or a Google sign-in. Distinct from authorisation, which decides what they may do. Learn more
- Row Level Security (RLS)
- Database rules that decide, per row, who may read or change data. Without RLS policies a table is either locked or wide open — never leave it to chance. Learn more
- Secret / API key
- A private credential for another service. Secrets belong in server-side storage, never pasted into front-end code where visitors can read them. Learn more
- User roles
- Labels like admin or member, stored in their own table and checked on the server, that control which parts of an app someone can use. Learn more
Publishing & SEO
- Analytics
- Measurement of what visitors do on your site. In the EU and UK it usually needs consent before tracking scripts load. Learn more
- Core Web Vitals
- Google's speed and stability measures — loading, responsiveness and layout shift — that affect both ranking and how fast your site feels. Learn more
- Custom domain
- Your own web address (like yoursite.com) pointed at your published Lovable app through DNS records. Learn more
- Deployment
- The build-and-upload step that turns your project into the files served to visitors. A failed deployment leaves the previous version live.
- DNS records
- Settings at your domain registrar (A, CNAME, TXT) that tell the internet where your site lives and prove you own the domain. Learn more
- Open Graph image
- The preview picture and text used when a link is shared on social apps, set with og: tags on each page.
- Publish
- Pushing your current build to a public URL. Changes made after publishing stay in preview until you publish again. Learn more
- robots.txt
- A small file telling crawlers which paths they may fetch. A stray Disallow: / hides your entire site from search.
- SEO
- Making pages easy for search engines to find, understand and rank: clear titles, useful descriptions, real routes and internal links. Learn more
- Sitemap
- A machine-readable list of your public pages at /sitemap.xml, submitted to Google so new pages get discovered faster. Learn more
- Structured data (schema)
- Extra machine-readable markup describing what a page is — an article, a product, an FAQ — which helps search and AI engines quote it correctly.
Web fundamentals
- Caching
- Storing a copy of something so it need not be fetched again. Great for speed, and the usual reason an updated page still looks old. Learn more
- Component
- A reusable piece of interface — a button, card or header — defined once and used across pages so one change updates them all.
- Design system / tokens
- The shared colours, fonts and spacing values your app reuses. Editing a token restyles the whole site consistently. Learn more
- Responsive design
- Layout that adapts to screen size so the same page works on phone, tablet and desktop without a separate mobile site. Learn more
- Route / page
- A distinct URL in your app, like /pricing. Each route can carry its own title and description, which is why real pages beat scroll anchors for search.
- State
- Information the interface is holding right now — a form's current values, whether a menu is open. Lost on refresh unless saved to the database.
