Skip to content
try reference course saved
English
Level 3: The Software World
Lesson 2 · +10 XP

Frontend and backend

You open Instagram. You see a feed. You scroll, double-tap a photo, leave a comment. Feels like one thing — one app doing one job.

It’s not. It’s two.

The frontend is the part of the software you see and interact with. The backend is the part that lives somewhere else, holds the data, and does the heavy lifting.

The app on your phone is the frontend. When you double-tap that photo, a tiny message goes off to Meta’s computers — that’s the backend — saying “this user liked this post.” The backend writes it down. Next time anyone loads that post, the backend tells them: “42,318 likes.”

Why it’s split

Three reasons this split shows up almost everywhere:

  • The frontend has to look good. Buttons, layouts, animations, dark mode. It runs on whatever device the user has.
  • The backend has to be the source of truth. Likes, messages, your account balance — those can’t live only on your phone, because then a different phone wouldn’t see them.
  • Different skills. Designing a beautiful screen is a different job from designing a system that handles ten million likes a second. Different people often do them.

So most teams build two programs and let them talk to each other.

The thing that trips people up

Frontend and backend aren’t physical places. They’re roles.

The frontend code might live in the same repo as the backend code. They’re often written by people sitting in the same room. The line between them isn’t “two different products” — it’s “two different jobs the software is doing.”

The clearest signal: the frontend runs on the user’s device. The backend runs somewhere else. When you close Instagram, the frontend goes away. The backend keeps running, holding everyone’s posts, waiting for the next phone to ask.

”Full-stack” — the word you’ll hear

You’ll hear developers describe themselves as frontend, backend, or full-stack.

  • Frontend dev — works on what the user sees.
  • Backend dev — works on the part the user doesn’t see.
  • Full-stack dev — works on both. Not a superhero, just someone comfortable in either half.

When Claude tells you “this is a full-stack app,” it means the codebase you’re looking at contains both halves.

What’s next

Now we name the conversation between these two halves. There’s a word for the program that asks (the frontend, usually) and a word for the program that answers (the backend, usually). They’re called client and server.