Build Your First App in 10 Minutes
Module 1 · First Spark

Build Your First App in 10 Minutes

Do it before you understand it: describe an app in plain English and watch a working version appear.

🛠️ Learning by Doing

No slides. No vocabulary list. Just open the tool you picked in Module 0 and build something.

Here’s the target — a finished version of the exact app you’re about to build:

my-about-me-page MC Maya Chen Loves maps, ramen, and tiny side projects 🌍 I've set foot in 12 countries Show me a fact

That’s what “a soft blue about-me page with a random fun-fact button” looks like once an AI builds it. Yours will come out a little different — different name, different colors, different facts — and that’s exactly right. This is a target to aim near, not a copy to match.

💻 Code Lab: Your First Build

Step 1 — Open your tool and describe your app.

Copy this prompt, or write your own idea instead:

“Build me a simple web app: a personal ‘about me’ page with my name, three fun facts about me, and a button that shows a random fun fact when clicked. Use a clean, friendly design with a soft blue color scheme.”

Step 2 — Run it.

Most tools show you a working preview right in the chat, or give you a button to open it. Click it. Look at what actually appeared. If the tool instead gives you an HTML file, save it and double-click it — it opens in your browser and runs, exactly the same way.

Don’t see a preview or a file anywhere? Don’t hunt around guessing — ask directly: “Where do I click to see this running?” (Module 0 covers why this works every time, even as interfaces change.)

Step 3 — Poke at it.

Click the button a few times. Does it show a different fact? Does anything look off? Don’t fix anything yet — just notice.

Step 4 — Tell someone (even if it’s just yourself).

Say out loud what you just did: “I described an app in plain English, and it exists now.” That sentence is the entire point of this lesson.


🔍 Notice What You Did Not Do

You didn’t write a single line of code. You didn’t open a technical manual. You didn’t debug a syntax error before anything ran. You described an outcome, and a working version of that outcome appeared.

Hold onto exactly what that felt like — confusing, exciting, maybe a little unbelievable. The next lesson explains why it worked. Right now, you just need the experience of it working.

⚠️ Common Pitfall: Don't Rewrite From Scratch If Something's Off

If the fun-fact button doesn’t quite work, or the colors aren’t what you pictured, the instinct is to scrap it and start over with a longer, “more careful” prompt. Resist that.

The fix isn’t a better first prompt — it’s a second sentence. You’ll learn exactly how to do that refinement in Module 2. For now, if something’s off, just note it and move on to the next lesson.


⏭️ Up Next

You built something. Now let’s actually name what just happened — what vibe coding is, and why this works at all.