The First Build
After this drill, you have generated a working web application from your spec using Lovable.dev.
Why this matters
This is the drill where the belief breaks: 'I could never build software.' You will take the spec you wrote in Drill 3.1, paste it into Lovable.dev, and watch a working web application appear. It will not be perfect. It will not be exactly what you imagined. But it will be real, interactive, and running in a browser. That moment — seeing something you described turn into something you can click — is where the course turns a corner.
How to do it
- 1
Create an account at lovable.dev if you have not already
The free tier gives you enough to complete this module. Sign in with Google or email.
- 2
Use the Lovable Build prompt to initiate the first build
Paste your trimmed spec from Drill 3.1 into Lovable. The first prompt sets the entire project direction.
- 3
Let Lovable generate the first version — do not interrupt it
The build typically takes 30–90 seconds. Watch the code being written in real time. Do not send another prompt until it finishes.
- 4
Preview the app and test the core functionality
Click every button. Fill in every form field. Does the core user action work? Note what works and what does not — you will fix it in Drill 3.3.
The prompt
Build a web application with the following specification: [PASTE YOUR TRIMMED SPEC FROM DRILL 3.1] Technical requirements: - Clean, modern UI using standard components - Fully functional (not a mockup) — the core user actions should actually work - Responsive (works on mobile and desktop) - Light mode by default Start with the most important user action and build that first. Do not add features not in the spec.
Success criteria
- ✓You have a running web application in Lovable
- ✓The core user action from your spec is functional (not just displayed)
- ✓You tested all interactive elements and know what works and what does not
- ✓You can describe three specific improvements you want to make in Drill 3.3
Common mistakes
Interrupting the build with follow-up prompts
→ Sending additional prompts while Lovable is building causes confusion. Wait for the build to complete, preview the result, then send one focused improvement request.
Judging the first build as a failure if it looks rough
→ The first build establishes the architecture. Iteration 1 (Drill 3.3) makes it good. Iteration 2 makes it polished. Do not judge a first draft by final-draft standards.