In a restaurant you only see the dining room. The real work happens behind the swinging doors.
A restaurant has two halves. The dining room has the tables, the menus and the friendly staff: everything guests see. Behind the swinging doors is the kitchen, with the stoves, the stock and the cooks.
Apps and websites are built the same way. The frontend is the dining room: the screens, buttons and words you see. The backend is the kitchen: the hidden part that stores information and does the work.
Who does what
- Frontend: how it looks, what happens when you tap, making it work on phones
- Backend: saving your account, checking your password, working out prices, sending emails
When you tap “Order”, the frontend passes your order to the backend. The backend checks it, saves it in a database and sends back “Order confirmed”.
What it isn’t
It isn’t your phone versus the internet. Some frontend code runs on your device, but some backend jobs can too. The split is about the role, not the place.
Where the comparison breaks down
A kitchen serves only its own dining room. One backend can serve many frontends at once: a website, an iPhone app and an Android app can all order from the same kitchen.
How the words fit together
The frontend talks to the backend through an API. The backend runs on a server and keeps information in a database.
When someone says full-stack, they mean a person who works on both the frontend and the backend.

When you'll hear it
“It's a frontend bug.” Something's wrong with what you see on the screen, not with the data behind it.
“The backend is down.” The hidden part that stores and fetches data isn't working, so the app can't load anything.
“She's a frontend developer.” She builds the screens, buttons and layouts people use.
“Is this problem in what people see, or in the data behind it?”


