Which Tools, and Why This Page Ages Fastest
Why This Page Ages Fastest
The rest of this course avoids naming products, on purpose. Names go stale; the ideas behind them do not. That leaves a real gap, though. You have just been told you can build something, so you reasonably want to know what to open. This lesson answers that, with one warning attached. This page dates faster than any other page in the library. Products here launch, merge, get bought and disappear inside a year. Free tiers shrink, features move between tools, and a clear leader today can be an afterthought by next spring. So treat every name below as an example at the time of writing, not a recommendation and not a ranking. Before you commit time or money, check what is current: a recent comparison, a colleague who builds, a forum where people are actually shipping. The categories are the durable part. They have been stable for years and will outlast the products filling them.
- Every product name here is an example at the time of writing, not a recommendation
- This page goes out of date faster than anything else in the library
- Check what is current before you commit time or money to any tool
- The four categories have been stable for years; the names inside them have not
- Nothing here is ranked — the right tool depends on what you are making
Four Kinds of Tool
Chat assistants are a conversation window. You describe what you want, code or instructions come back, and you copy them somewhere yourself. Examples at the time of writing: Claude, ChatGPT, Gemini. In-editor assistants work alongside you, inside the place your code lives. They can read every file in your project and change several at once, which suits editing something that already exists. Examples: Cursor, GitHub Copilot, Claude Code. Prompt-to-app builders take a description and hand back a whole working site or app, already running on the internet. Examples: Lovable, Replit, Bolt, v0. Hosting and database services are the plumbing underneath. Hosting puts your pages on the internet at a real address; a database stores the information your app keeps. Examples: Vercel, Netlify, Supabase, Firebase. Builders usually bundle hosting and a database for you. The other categories do not, so you choose them yourself.
- Chat assistants: the most flexible, but you decide where the code ends up
- In-editor assistants: see your whole project, best for changing work that exists
- Prompt-to-app builders: fastest route to something live, least control underneath
- Hosting puts your app on the internet; a database keeps what it stores
- Builders bundle the plumbing; the other categories leave you to pick it
Choose by What You Are Making
Pick by the shape of your project, not by whichever tool is loudest this month. Making a landing page, a form or a small internal tool from nothing? A prompt-to-app builder gets you something live fastest. Changing something that already exists, or working with files you did not generate? An in-editor assistant fits better, because it can see the whole project at once. Just want a snippet explained, or one small script? A chat assistant is plenty, and there is nothing to set up. Building something with sign-in and saved records? You will need hosting and a database, whether bundled or chosen. Using two tools together is normal: a builder for the first version, an in-editor assistant once you outgrow it. Ignore claims that any tool replaces engineers. Judge a tool by one thing — whether it gets you to a working version you can check.
- Something new from nothing: a prompt-to-app builder is usually the fastest start
- Changing existing work: an in-editor assistant, because it can see every file
- A quick explanation or one small script: a chat assistant needs no setup
- Sign-in and saved records mean hosting and a database, bundled or chosen
- Using two tools together is normal, not a sign you picked the wrong one
Free Tiers, Real Costs, and What Transfers
Almost every tool here has a free tier, and that phrase usually means one of three things. A trial that expires. A monthly allowance of requests, builds or credits that resets. Or a genuinely free level, with limits low enough that real traffic passes them quickly. Free tiers are fine for learning, and fine for a prototype nobody else uses. Costs tend to start at the same three points. When you put something on the internet at your own address. When other people start using it. And when your app calls an AI service for every user, rather than just for you. That last one is charged by usage and has no ceiling unless you set one, which module five covers in detail. Whichever tool you choose, the skills in this course transfer. Writing a clear description, changing one thing at a time, keeping a working copy, reading an error message, testing as a stranger: none of that belongs to a product.
- "Free" usually means a trial, a resetting allowance, or a low-limit permanent tier
- Costs commonly start at your own address, at real users, and at AI calls per user
- Usage-based charges have no ceiling until you set one — module five covers this
- Check current limits yourself; published tiers change quietly and often
- Specs, small changes, saved copies and honest testing transfer to any tool
Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.