New to this? You're in the right place. This post doesn't assume you've built or deployed anything before. If a word needs explaining, it's explained right where it shows up. This is likely the most jargon-dense topic in this whole series, so take it slow — there's a lot of vocabulary packed in.
The one word everything else is building toward: deploying
Building an app on your own computer and having it actually usable by other people on the internet are two very different things. While you're building it, it only exists on your machine — nobody else can visit it. "Deploying" is the word for the step where your finished (or work-in-progress) app gets copied onto a computer that's reachable from the internet, so a real URL takes real visitors to it. Everything else in this guide is either preparing for that step or supporting it.
The vocabulary, one piece at a time
- Code is just the written instructions that make an app do what it does — text files, in a specific language a computer can follow.
- Version control is a system that keeps a complete history of every change ever made to your code — like "track changes" in a document, but far more powerful, letting you see exactly what changed, when, and by whom, and undo any of it.
- A repository (or "repo") is one project's entire history and current code, stored together. GitHub is the most common place to keep one online.
- An editor is the program you actually type code into — the word-processor equivalent for writing software.
- A terminal is a plain text-based way to give your computer direct instructions, instead of clicking buttons. It looks intimidating but is really just typing a command and pressing enter.
- An AI coding agent is a program that can read your code, suggest or make changes, and run commands for you inside that terminal — instead of you writing every single line by hand.
- Deploying (the word from above) puts your app on a computer reachable from the internet, at a real address.
- A database is where an app's actual data lives — user accounts, saved records, anything that needs to persist between visits, as opposed to the app's code, which just describes how it behaves.
Why this involves so many different tools
Each of the pieces above used to require setting up and maintaining your own dedicated computer for it. What's changed is that a whole ecosystem of services now handles each piece for you, the way managed hosting handles a website's maintenance — a service for keeping your code's history, a service that automatically deploys your app the moment you save a change, a service that runs your database without you administering a computer at all. You're not setting up infrastructure from scratch; you're connecting a handful of specialized services that each do one job well.
What actually happens when you "push code" and it goes live
Here's the part that feels like magic the first time you see it: once your code's history-tracking service (GitHub) is connected to your deployment service, saving and uploading a change to your code can trigger the deployment service to automatically rebuild and republish your app within seconds — no manual step where someone has to remember to "put it live." You make a change, save it, and a few seconds later the real website has that change on it.
What this isn't
An honest note, because overselling doesn't help anyone: none of this makes building an app easy by itself — it removes the infrastructure work (servers, maintenance, security patching), not the work of actually designing and writing the app. And an AI coding agent speeds up writing code; it doesn't replace understanding what the app is supposed to do or reviewing what it produces.
Ready for the deeper version?
Everything above is the plain-language shape of a real, hands-on technical guide — with copy-pasteable commands — to actually setting all of this up and deploying a real app. If you want the real detail, the full version is here: Build and Deploy a Next.js App with Claude, Vercel, and Supabase.
If this was your first time reading about any of this, you now know enough of the vocabulary to follow that post without getting lost in the first paragraph.