Library / Data & backend / Frontend
No. 041·noun·also called front end, client, UI

Frontend

The part of an app you see and touch in the browser or on your phone: screens, buttons, and forms.

SPECIMEN · DIAGRAM · LAYERS
FrontendScreens, buttons, forms (on your device)
APIThe messages between them
BackendRules and logic (on a server)
DatabaseWhere data is kept
Definition

What it is

The frontend is everything that runs on the person's device: the layout, the buttons, the animations, what happens when you click. It's the restaurant's dining room.

The frontend asks the backend for data and sends it changes, but it can't be trusted with secrets or rules. Anyone can poke at code running in their own browser, so checks like "only admins can delete" must also live on the backend.

When something looks wrong, it's usually a frontend issue. When something is saved wrong or shown to the wrong person, it's usually a backend one.

Say it like a builder

How to ask for it

Vague

“The app is broken, the button doesn't look right on the order page.”

Precise

“Frontend issue on the Orders page: the "Refund" button overlaps the total on screens under 400px wide. Data and saving are fine; only the layout needs fixing.”

Why it works

Naming it a frontend issue tells the builder where to look and what not to touch.

In the wild

You've seen this in

  • GEverything you see in Gmail
  • TThe Instagram app's screens
  • AThe checkout form on any store
Usage note

Often confused with