What is a frontend, actually?

The frontend is the part of your app that people see and touch: the screens, the buttons, the forms, the colors, the words. If you can point at it on your phone or click it in a browser, it is frontend. Everything working behind the scenes, where the data lives and the rules run, is the backend.

That one split, frontend and backend, is the most important sentence in all of software. Every tool you will use, every error you will read, and every developer you will ever talk to assumes you know which side of the line you are pointing at. Learn this word first and half the jargon falls over on its own.

What counts as the frontend?

Everything a user experiences directly. Open any app you love and start pointing: the homepage, the login screen, the menu that slides open, the button that turns from grey to green when you finish a form. All of it is frontend. A useful test: if a user could screenshot it, it is frontend.

• Every screen and page: the homepage, the dashboard, the settings page, the checkout.
• Everything you interact with: buttons, forms, menus, toggles, search boxes.
• Everything that makes it look right: colors, fonts, spacing, and the layout that rearranges itself on a phone.
• Everything that responds as you act: the error that appears when you mistype your email, the cart count that ticks up.

What's the backend, then?

The backend is everything users never see: where your data is stored, where logins are checked, where payments actually move. The frontend asks, the backend answers. When someone signs into your app, the frontend is the login form; the backend is the machinery that checks the password and remembers them.

Think of a restaurant. The frontend is the dining room: the menu, the tables, the lighting, everything arranged for the guest. The backend is the kitchen: invisible from your seat, doing the real work, judged entirely by what comes through the door. The kitchen has its own lesson in this stage: what a backend is, and where your data lives.

Why does the word matter if AI writes the code?

Because every conversation about your product splits along this line, and your tools assume you know it. Your prompts get sharper the moment you can say which half you mean. 'Make the signup button bigger' is a frontend request. 'Remember which plan each user picked' is a backend request. Same app, completely different work.

It is also how you read problems. If something looks wrong, sits in the wrong place, or feels clumsy to use, that is a frontend issue, and usually a quick fix. If the wrong data shows up, a login fails, or something a user saved has vanished, that is a backend issue, and it deserves more care. Knowing which kind of broken you are looking at is half of debugging.

And when you eventually hire help, quotes split this way too. A developer who hears you use these words correctly gives you a straighter quote, because you have just told them you cannot be hand-waved.

What is a frontend actually made of?

Under the hood, three layers with unfriendly names do friendly jobs. HTML is the content and structure: the headlines, paragraphs, and boxes. CSS is the appearance: the colors, fonts, and layout. JavaScript is the behavior: what happens when someone clicks, types, or scrolls. Every website you have ever visited is these three.

Modern apps bundle those layers into reusable pieces called components, using frameworks with names like React and Next.js. You do not need to learn any of them. But recognize the names, because your AI tools will mention them constantly, and now you will know they are just talking about the visible half of your app. When Lovable or Bolt generates your project, this is what comes out the other end.

How do I use this tomorrow?

Describe frontend requests in user language: what someone sees, where it sits, what should happen when they touch it. Let the tool worry about the wiring. And when something misbehaves, say which side you suspect. 'The page looks broken on my phone' and 'the form submits but nothing saves' send your AI builder down two completely different roads, and both sentences are now yours.

Hear a word you don't recognize? The Language glossary translates the whole vocabulary, and each term links out to its full lesson as it publishes.

Common questions