Get Started
Use AI properly

Mission 9 of 11

Build your first app without coding, and get your own link.

Go from a blank box to a working web app with its own link, built by describing it in plain English. Then send that link to a mate. No code, no install, no card.

40 minBeginnerFree toolsFree mission

What you'll do

Describe your app and watch it appear

Sign up to Lovable, paste a five-part brief, and see a working bill splitter on your screen.

Test it, change it and fix it

Check the sums with numbers you can verify, add a feature by talking to it, and report bugs properly.

Publish it and send the link

Learn what must never go in your app, publish for free, and watch someone else use something you made.

  • A five-part brief you can reuse to describe any app to any AI builder
  • A clear picture of what spends credits and what's free
  • The one safety rule that keeps passwords and keys out of public view
Before you start
  • A browser on a computer. A phone is handy for the final test
  • An email address, or a Google, GitHub or Apple account, for a free Lovable ↗ account. No card needed
  • To be 18 or over, or to have a parent or guardian's permission (that's in Lovable's terms)
  • A calculator for about two minutes in step 3. Your phone's is fine
Your progress0/7
● What you'll have in 40 minutes
Preview
The whole journey in 20 seconds, as an illustration: brief, build, publish, live link. Your app will look a little different.
01/07Open Lovable and claim your free credits0 done
STEP 01 of 07~4 min

Open Lovable and claim your free credits

Get into the best free builder for a first app, knowing exactly what you've got to spend.

Before you can build anything, you need a builder to describe it to. This step picks one and gets you signed up.

Meet your builderLovable is like having a developer on the other end of a chat window. You describe the app, it writes everything, and you watch it run next to the conversation.

  • Why Lovable for your first app: publishing from the Publish dialog is free, every plan gets a lovable.app address, and you get free allowances for fixes and small text edits.
  • Bolt is the strongest backup: 300,000 tokens a day and 1 million a month, with free hosting on a bolt.host address.
  • Google AI Studio can publish up to two apps on its Starter Tier with no billing account, but Workspace accounts and anyone with a past paid Google Cloud account don't qualify.
  • v0 gives you 7 messages a day. Replit gives you one free published app, and its link goes down after 30 days. That's why they're not our pick today.
  1. Check what the free plan covers. Open Lovable's pricing page ↗ and click Free grants on the Free card.

    From Lovable's pricing page. Build credits are what you'll spend on this course.

    The card shows 5 build credits a day, up to 30 a month.

    Tip
    The small print that matters. The Free plan also includes a daily chat allowance and up to 5 lovable.app addresses. Custom domains and removing the "Edit with Lovable" badge are on paid plans, and you need neither today.
  2. Sign up. Go to lovable.dev/signup ↗ and use email, Google, GitHub or Apple.

    You land on your dashboard with a big prompt box in the middle.

  3. Switch off model training. Click your avatar at the bottom left, choose Account settings, open Preferences, find AI model training and turn off Use my Lovable content for model training.

    Tip
    Why bother? Since September 2026, Lovable may use prompts and code from Free and Pro plans to train its models unless you opt out. It's free, takes 20 seconds and changes nothing about how the app builder works.
Checkpoint
You're signed in and can see the prompt box on your dashboard, and the model training toggle is off.
If it breaksIt says I've been denied because of suspicious activity + 1 more
It says I've been denied because of suspicious activity
Turn off any VPN or proxy, wait a few minutes and try again from your usual browser. If it still refuses you, email support@lovable.dev from the address you used, or follow this course in Bolt ↗ instead. The brief and the bug formula work there too.
I can't find the training setting
Go straight to your account settings ↗ and open Preferences. If you can't see it, carry on and keep private details out of your prompts, which you should do anyway.
Still stuck? Ask the community
STEP 02 of 07~6 min

Describe your app and watch it appear

Learn the five-part brief, send it, and have a working app on your screen inside the next few minutes.

You're signed in, so now you tell the builder what to make.

The five-part brief

An AI builder is a brilliant new starter on their first day: fast and keen, and it fills every gap with a guess.

A good brief leaves fewer gaps. Here are the five parts.

See the difference it makesHere's the same idea written two ways.

  • Weak: "Make me a bill splitting app." The builder has to guess everything. It might add accounts, saved groups, a database and images. That's more credits spent and more things to break.
  • Strong: the brief below. It says what goes in, what comes out, what must always be true and what to skip. Part 5, Leave out, does more for your credits than anything else in this course.

Send it

  1. Copy the brief. Use the copy button on this box.

    Paste into Lovable
    Build a one-screen bill splitter web app called Fair Split, for friends paying for a meal together.
    
    What it does: I enter the bill in pounds, choose a service charge (0%, 10%, 12.5% or my own percentage) and set how many people are paying. It instantly shows the new total and what each person pays, in a list: Person 1, Person 2 and so on.
    
    Rules:
    - Show money with a £ sign and 2 decimal places.
    - The amounts must always add up to exactly the new total. If it doesn't divide evenly, the first people pay 1p more.
    - If the bill is empty or the number of people is below 1, show a friendly message, not an error.
    
    Look: dark background, one big bold result, large buttons, designed for a phone first.
    
    Leave out: no login, no database, no images, no payments. Nothing else on the page.
  2. Paste it. Click inside the prompt box on your dashboard and paste. That's marker 1.

    Where to paste your brief. The heading and the example wording in the box change, so don't worry if yours differs.
  3. Check the mode. The picker at marker 2 should say Build. If it says something else, click it and choose Build.

  4. Send it. Click the arrow at marker 3.

    Lovable creates your project and opens the editor.

    Watch it buildThe first version takes a few minutes. Lovable shows its progress in the chat on the left, and your app appears on the right.

    Tip
    Why no images? Generating images adds to the bill, and a calculator doesn't need them. Lovable's own example of a landing page with generated images costs about 2 credits. Save your credits for the parts that make the app work.
Checkpoint
The editor is open with a chat on the left and your Fair Split app running on the right. You can type in it. You've just built an app.
If it breaksIt's asking me questions instead of building + 3 more
It's asking me questions instead of building
Good sign. It's filling gaps with you instead of guessing. Answer in plain English and keep your answers short. If you're not sure, say "keep it as simple as possible".
It stopped halfway and says I'm out of credits
Your work is safe. Daily build credits refresh at 00:00 UTC, which is midnight in the UK in winter and 1am in summer. Come back then and select Resume on the paused card.
It says I have no build credits at all
The Free plan's daily credits stop once 30 have been granted in a calendar month, and restart on the 1st. If you can't wait, paste the same brief into Bolt ↗, whose free tier runs on tokens instead. The rest of this course's method carries over.
The result looks nothing like the pictures here
That's normal. Every build comes out a little different. What matters is that the sums work, and you'll check that next.
Still stuck? Ask the community
STEP 03 of 07~7 min

Test it like a suspicious customer, then add a feature

Prove the app works with numbers you can check, then make your first change by talking to it.

Your app is running, but looking right isn't the same as being right. This step checks the sums, then changes the app.

Test it

Find your way aroundThe chat is at marker 1. The live app is at marker 2. Everything you click in the preview behaves as it will for real visitors.

Where to look in the editor.
  1. Run these four tests in the preview. Type each one into your app and compare the result.

    • £47.50 with 10% and 3 people: new total £52.25. People pay £17.42, £17.42 and £17.41.
    • £86.40 with 12.5% and 4 people: new total £97.20. Everyone pays £24.30.
    • £100 with 0% and 3 people: people pay £33.34, £33.33 and £33.33.
    • Empty bill: a friendly message, not a blank screen or an error.
    Tip
    Why these numbers? The first and third don't divide evenly, and that's where rounding bugs hide. Three lots of £17.42 is £52.26, a penny too much. An app can look perfect and still be wrong, so always test with sums you've worked out yourself.
  2. Check the phone view. Click the device toggle at marker 3 until you reach Mobile view.

    Most people will open your link on a phone, so look for squashed text and buttons that are hard to tap.

  3. Your turn: invent a test. Make up your own bill, service charge and number of people. Work out the answer on your calculator first, then try it in the app.

    Tip
    Stuck? Pick a number of people that doesn't go neatly into most totals. Think about which group sizes leave a stray penny or two, then add the list up by hand.

Ask for a change

Say exactly what to add, where it goes and what it does. Finish with "Change nothing else", because otherwise a builder may tidy things you were happy with.

  • Weak: "Make it easier to share." It could add anything.
  • Strong: the prompt below. One feature, one place, one exact behaviour.

Here's the strong prompt in full.

Paste into the Lovable chat
Add a Copy button under the list of people. When I click it, copy this text to the clipboard using the current numbers: "Fair Split: total £52.25 between 3 people. Person 1 £17.42, Person 2 £17.42, Person 3 £17.41." Change nothing else.
  1. Your turn: send a change of your own. Use the prompt above, or write your own small feature, such as a button that resets everything. Type it into the chat box and send it.

    Tip
    Stuck? Answer three questions and you've got your prompt: what's the thing called, where on the screen does it go, and what happens the moment someone uses it? Then end with "Change nothing else".
Checkpoint
Your own test passes, the app looks right in Mobile view, and your new feature works in the preview.
If it breaksOne of the tests gave the wrong answer + 1 more
One of the tests gave the wrong answer
Perfect timing. Step 4 is about exactly this. Note what you typed and what it showed, and carry on.
I can't see the device toggle
It sits in the row above the preview. In a narrow window some controls fold away, so make your browser window wider.
Still stuck? Ask the community
STEP 04 of 07~7 min

Fix bugs by talking to it

Turn "it's broken" into a message the builder can act on, and know what to do when the first fix fails.

Sooner or later something will come out wrong. This step covers how to report it.

Report a bug

  1. If a build error appears, click Try to fix. The button shows up on the activity card in the chat.

    Give it one or two goes. Your account includes 10 free fixes, and each one comes back 24 hours after you use it.

    If the app runs but gives a wrong answer, report itBuilders fix what you can point at.

  2. Fill in this formula and send it in the chat.

    Bug report formula
    Where: [which part of the screen]
    What I did: [the exact numbers or clicks]
    What I expected: [the right result]
    What I got: [the wrong result]
    Fix only this. Keep everything else as it is.
    Demo
    An illustration of a good bug report at work: exact numbers in, a one-penny rounding bug out.
    • Before: "It doesn't work, fix it!" The builder has nothing to aim at, so it guesses and you pay for the guess.
    • After: "In the people list, I entered £47.50, 10% and 3 people. I expected the amounts to add up to £52.25. They add up to £52.26. Fix only this."
    • Why it's better: the builder can reproduce it, knows what right looks like, and won't touch anything else.
    Tip
    Show, don't tell. For layout problems, attach a screenshot of the broken screen to your message. It's quicker than describing it and it leaves less room for a wrong guess.
  3. Your turn: rewrite a bad bug report. A friend says, "The split is wrong when there are loads of people." Write it out properly using the formula, as if you'd seen the bug yourself. You can make up the numbers.

    Tip
    Stuck? Look at the words "wrong" and "loads". Neither tells the builder anything. Swap each one for a number, then say what the number should have been.

When the first fix fails

Learn the ladderWhen a fix doesn't work, don't send the same request again. Move up a rung.

  1. Rung 3: ask why before you build. Open the mode picker next to the chat box, choose Chat.

    Chat mode talks it through without touching your code, and a message typically costs a fraction of a credit. Send this:

    Paste into Chat mode
    This bug keeps coming back. What is the root cause? Explain it in simple terms before proposing a fix, and list what we've already tried so we don't repeat it.
  2. Rung 4: go back in time. Click the History toggle at marker 2, click the last version that worked, then click Revert and confirm.

    Where to find History. Marker 1 is where your bug reports go.
    Tip
    The version trick. Every change saves a version on its own, so nothing you do can break your app for good. Before anything risky, bookmark a working version in History so it's one click away. Reverting doesn't refund credits, so go back early rather than paying for a pile of patches.
Checkpoint
You've written a bug report in the four-part formula, and you can find the History toggle in your editor.
If it breaksThe fix broke something else + 1 more
The fix broke something else
Say so, and link the two: "We fixed the rounding and now the Copy button shows old numbers. Could the fix have caused this?" If it gets tangled, revert to the last good version and ask again in smaller steps.
My app has no bugs, so what do I practise on?
Lucky you. Keep the formula to hand anyway. Next time you add a feature, retest all four sums from step 3, because new features are how old bugs get in.
Still stuck? Ask the community
STEP 05 of 07~6 min

Spend your credits like they're your own money

Know what's free, what's cheap and what eats your daily 5, so you never get stuck halfway.

Your build credits are a small daily allowance. This step shows where they go, so you don't run dry halfway through.

Learn the price listYour 5 daily build credits don't get spent evenly. Some moves are free, and they're the ones people forget about.

See what Build mode costsLovable publishes these examples. Costs depend on the work done, so a small change is cheap and a big generation isn't.

From Lovable's credits docs. These are its illustrative examples, so your costs will vary.
  1. Check your balance. Click the menu icon at the top left of the editor, then your workspace name. Hold your pointer over the info icon next to Free usage included.

    Where to see your balance (1) and what one reply cost (2 and 3). The numbers here are examples.
  2. Check what your last message cost. Under Lovable's latest reply, open the More options menu (the three dots at marker 2) and read Credits used at marker 3.

  3. Change some words for free. In the toolbar at the bottom of the preview, click Edit text inline (the T icon), click your app's heading, type a new one and click Send.

    The preview toolbar. The T icon is Edit text inline, and you get 100 free edits, each back after 24 hours.

The five habits

These stretch a small allowance a long way.

  • One change at a time. Check the preview after each. If something breaks, you know which change did it.
  • Talk in Chat mode first. Questions and ideas are typically a fraction of a credit, and your daily chat allowance covers them first. Switch to Build when you've decided.
  • Stop a wrong turn early. Click the stop button as soon as it heads the wrong way. You only pay for the work done so far.
  • Publish from the dialog, never the chat. The dialog is free. Asking in chat uses build credits.
  • Leave out what you don't need. No logins, databases or generated images until you've got a reason.
Tip
Know the clock. Daily build credits refresh at 00:00 UTC and don't roll over. The Free plan also stops granting them once it hits 30 in a calendar month, then restarts on the 1st. There's no card on the Free plan, so running out just means waiting, never a surprise bill.
Checkpoint
You know how many credits you have left, you've seen what a message cost, and your app's heading has changed without spending a credit.
If it breaksEdit text inline is greyed out or won't switch + 1 more
Edit text inline is greyed out or won't switch
Finish or discard whatever you were doing in the toolbar first. Other modes stay unavailable while you have an unsent change.
I can't see the toolbar
It may be hidden. Click the Show preview toolbar icon in the row above the preview, next to Share and Publish.
Still stuck? Ask the community
STEP 06 of 07~5 min

Keep your secrets out of the shop window

Learn the one rule that stops an embarrassing leak before your app goes public.

Your app is about to go public, so this is the moment to learn what must never go into it.

Understand the two roomsYour app's pages run in each visitor's own browser, so the code sent to them can be read by anyone. Only code on a server stays behind the counter.

Warning
Never put an API key, password, bank detail or anyone's personal information in your prompts or your app. An API key works like a credit card for an online service. If it leaks, a stranger can run up charges on your account. Fair Split needs no keys and no personal data, so keep it that way.

Use made-up dataWhen you test or demo anything, use Person 1, £47.50 and made-up details. Never paste in real customer lists, medical details or your mates' phone numbers.

  1. Check your app. Open the mode picker, choose Chat and send this prompt from Lovable's own security guide.

    Paste into Chat mode
    Review frontend code for exposed secrets, API keys, or sensitive information
  2. Your turn: spot the danger. Three friends send you these requests. Decide which are safe to type into a builder, and how you'd handle the others.

    • "Add a payment button. Here's my key: sk_live_..."
    • "Put my customers' names and phone numbers in the list."
    • "Add a light and dark theme switch."
    Tip
    Stuck? Picture the app's code printed on a poster outside a pub. Which of those three would you be happy to see up there? That's your answer.

    Know the safe route for laterWhen a future app really needs a key, ask for it this way. Lovable then asks for it through a secure form and stores it as a Secret, away from the browser.

    For a future app
    Connect [the service]. Ask me for any API keys you need, and never put them in the frontend code.
    Warning
    If a key ever leaks, delete it at the service that issued it and make a new one, straight away. Removing it from your app isn't enough, because anyone who copied it can still use it. Logins, payments and customer data also need proper checks, so learn those before you take real data from real people.
Checkpoint
The scan reports nothing sensitive in Fair Split, and you've worked out that only the theme switch is safe to send as written.
If it breaksI already pasted a key or password somewhere + 1 more
I already pasted a key or password somewhere
Treat it as leaked. Change the password or delete the key at the service that issued it, then make a new one. Do this first and tidy up afterwards.
The scan flagged something I don't understand
Stay in Chat mode and ask: "Explain this finding in simple terms. Is it a real risk for an app with no login, no database and no keys?" Fix it before you publish if it's real.
Still stuck? Ask the community
STEP 07 of 07~5 min

Publish it and get your link

Turn your project into a link anyone can open, then learn how to update it.

You've tested the app and checked it for secrets, so now you publish it. That gives you a link you can send to other people.

  1. Open the dialog. Click Publish at the top right of the editor. That's marker 1.

    Where to click to publish. The address here is an example.
  2. Choose your address. Keep the suggested Website URL at marker 2 or edit it. Short and readable beats clever, and it ends in .lovable.app.

  3. Check who can see it. The row at marker 3 should read Visible to anyone with the link. If you'd rather keep it to friends, click the row and choose Invite only, which covers up to 10 people.

  4. Read the security line. Lovable runs a quick scan by itself, shown at marker 4. If it reports issues, click the line and review them before going on.

  5. Publish. Click the blue Publish button at marker 5 and wait for Your website is live.

    Tip
    Yes, this is free. Publishing from this dialog costs no credits and works even on a zero balance. Your link has no fixed expiry date, though Lovable may unpublish a Free app after 12 months with no visits and no owner logins. It emails you if that happens, and you can publish it again.
  6. Test the link on your phone. Click Copy link, send it to yourself and open it on your phone. Run the £47.50 test one more time.

  7. Send it to someone. Message the link to a mate and ask them to split your last meal out.

    Watching someone else use it is the best bug report you'll ever get.

    Learn how updates workYour live site is a snapshot, so later changes stay in the preview until you say so. Change something, click Publish, then click Publish changes. A small dot on the button means you've got changes waiting.

    Tip
    Where to go next. You've built a tool. A product is the next level: real users, sign-in and a database that keeps their data apart. That's what Build your MVP in a weekend, not a quarter teaches, one screen at a time.
Checkpoint
Your app opens on your phone at your own lovable.app link, and the sums are right. It's live.
If it breaksThe dialog won't let me publish + 3 more
The dialog won't let me publish
If the latest build failed, publishing is blocked until it's fixed, and the dialog offers Try to fix. Click it, then try again.
My friend sees an old version
You probably changed something without republishing. Click Publish, then Publish changes, and ask them to refresh.
My link shows a blank page
Open it in a private window to rule out your browser. If it's still blank, tell Lovable: "My published app shows a blank screen, but the preview works." Include any error you can see.
There's a badge on my app
That's the "Edit with Lovable" badge, which stays on Free plan apps. It's fine for your first project. Removing it is a paid plan feature.
Still stuck? Ask the community

Your first wins

It works. Now do something with it.

Turn your own idea into a brief

Take something you do on paper or in your head, and get a brief for it. Paste the result into a new Lovable project.

Prompt
Turn my app idea into a brief for an AI app builder, in five parts: the job, what goes in and what comes out, the rules that must always be true, the look, and what to leave out. Keep it to one screen, with no login, no database and no images. Ask me up to 3 questions first if you need to.

My idea: [describe it in a sentence or two]

Make Fair Split properly useful

Add one feature at a time, check it and publish. Real names instead of Person 1 is a great first upgrade, because the names stay in the visitor's browser if you don't save them.

Prompt
Let me type a first name for each person instead of Person 1 and Person 2, and use those names in the list and the Copy text. Don't save the names anywhere. Change nothing else.

See what strangers can see

Open your live app on a computer and press F12 (on a Mac, Cmd+Option+I). Click the Sources tab and look around. Every visitor can read all of this, which is exactly why keys and private details never go in it.

Next: build a proper product

Ready for sign-in, a database and your first real users? Take the next step with Build your MVP in a weekend, not a quarter.

Undo it cleanly

How to remove everything this mission installed.

Take the app offline but keep the projectOpen Project settings, then Publishing, then Unpublish project. You can also click Publish, open the three-dot menu in the dialog and choose Unpublish.

Delete the projectOpen Project settings, then Danger zone, then Delete project, and type its name to confirm. The live link stops working within about a minute. You can restore it from workspace settings for 60 days, and after that it's gone for good.

Delete your accountUse Delete account in your Lovable account settings. It's permanent, so export anything you want to keep first.

Next mission · Use AI properlyClaude Code for complete non-coders: tidy your files, make a report, build a web page
→