If an app were an office, the frontend is the front desk and the backend is everything behind the door that makes the office function.
Stay with the office picture. A client walks up to the desk, fills out a form, signs a document, picks up a receipt. That’s the part they experience, but the front desk isn’t the whole business. Someone still has to look up the account, check the file, update the record, and send the confirmation. That hidden part is the backend. It talks to the database, runs rules, checks permissions, sends emails, and decides what happens next. The frontend makes the work usable; the backend makes the work real.
How it shows up
You’ll feel this when you build with AI. Ask an agent to “make me an app” and it may create a nice-looking screen first: buttons, forms, colors. That’s satisfying, but you still need to ask, “What happens when I click this?” If nothing is saved, fetched, or sent, you may only have a mockup.
The API is often the doorway between front desk and back office: the frontend asks in a structured way, and the backend answers. Sometimes the browser blocks that conversation because of CORS, a rule about which frontends can talk to which backends. A server is one place the backend runs.
Why you care
Frontend is how people touch the system; backend is how the system keeps its promises. You need both for software that works.