Skip to main content
Vibe Code Forum

Article: Front end, back end and full stack: who does what

Every web app has two halves. Knowing which half a problem is in makes it much easier to describe to your AI tool.

The front end

Everything that runs in the user's browser: the page layout, buttons, forms, animations and the code that reacts to clicks. It is written in HTML (structure), CSS (looks) and JavaScript (behaviour), often with a framework such as React, Vue or Svelte.

Key fact: everything in the front end can be seen by the user. Anyone can open the browser's developer tools and read the code, the data it receives and any key inside it. So the front end must never hold secrets or make decisions that matter for security.

The back end

Code that runs on a server you control (or a service such as Supabase acting as one). It:

  • talks to the database,
  • holds secret keys and calls paid APIs (AI, payments, email),
  • checks who the user is and what they are allowed to do,
  • runs scheduled jobs and handles webhooks from other services.

Users can't see or change back-end code, so it is where rules are enforced.

How they talk

The front end sends requests to the back end (for example "save this note", "give me my orders"), usually to addresses starting with /api/. The back end checks the request and replies with data. See APIs and API keys.

Full stack

"Full stack" means both halves. Frameworks such as Next.js, Nuxt, SvelteKit and Remix let one project hold both, which is why AI tools like them. Static sites (just pages, no server) have no back end at all; a service like Supabase can then act as one.

Use it in your prompts

  • "This is a front-end problem: the button doesn't change colour when clicked."
  • "Move the call to the AI API to the back end so the key isn't in the browser."
  • "Check on the server, not just in the page, that only the owner can delete a note."

Related: Databases for beginners, Sign-in and accounts.

More in Concepts