Show in graph
WEB

Product → Web Applications

Frontend

The user-facing part of a software system, often running in a browser or client application.

Motivation

Frontend is useful because it gives engineers a precise handle on a recurring problem: the user-facing part of a software system, often running in a browser or client application.. It helps you decide what to pay attention to, what abstractions are available, and which tradeoffs matter in real systems.

Where it fits

Frontend belongs to the Product track, inside the Web Applications layer. In the knowledge graph, this places it near concepts that explain the same level of abstraction and the neighboring ideas it depends on.

Mental model

Think of Frontend as one piece of the larger computing map. It is easiest to understand when you ask two questions: what problem does it solve, and what assumptions does it make about the concepts below it?

Common mistakes

  • Using Frontend as a buzzword without understanding the problem it solves.
  • Learning the definition in isolation instead of connecting it to nearby concepts.
  • Requires: Client, Browser
  • Relates to: API, Web Application