What Is a Terminal?

A terminal (also called a command line, console, or shell) is a text-based way to control your computer — instead of clicking icons and folders, you type commands and press Enter. It looks intimidating at first because there's no menu telling you what to do, but it's actually simpler underneath: every command is just a short word or two, and the same handful of commands cover almost everything you'll need.

"Terminal" and "shell" get used almost interchangeably, but technically: the terminal is the window itself, and the shell is the program running inside it that actually reads your commands and runs them. The most common shell is called Bash, which is why people often say "the Bash prompt" — it's the default shell on Linux and Mac, and available on Windows too (through Git Bash, which this whole track assumes you have).

The "shell" is the program that reads the commands you type and actually runs them, while the "terminal" is just the window it runs in.

Why bother, when clicking folders works fine? Because the terminal lets you do things a mouse can't: run a program with exact options, chain several steps together instantly, repeat the exact same action later without re-clicking through menus, and — most importantly for this track — every tool you'll use to actually ship a real project (Git, npm, Expo, deployment tools) is a command-line tool first. Some have a friendly app wrapped around them, but the terminal is the one interface all of them share.

You'll see a prompt — a short line ending in $ or > — waiting for you to type. After typing a command, press Enter to run it. If nothing seems to happen for a second, that's normal; some commands are just fast and quiet when they succeed. If something goes wrong, the terminal almost always prints an error message explaining what — reading that message is the single most useful debugging skill you can build.

$ 

What is the key practical reason this whole track uses the terminal instead of just apps with buttons?