frontend
The part of a software system that runs in the user's browser or device and presents the interface.
In more detail
Frontend engineering covers HTML, CSS, JavaScript and frameworks such as React. Design systems are a frontend concern shared across many applications.
Examples
In the browser: Frontend code is downloaded to each visitor and runs on their device, so it must be fast, accessible and safe even though you do not control the machine. This whole course is about how that code is parsed, laid out, scheduled, stored and secured.React is a frontend library.Related terms
- user interface — The part of a program people see and interact with, such as screens, buttons, text fields and menus.
- React — A JavaScript library for building user interfaces out of components, functions that return a description of what to show.
- design system — A shared set of design decisions, reusable components and rules that keeps every screen of a company's products looking and behaving the same way.
- backend — The server-side part of a web application that stores data and produces responses, as opposed to the frontend that runs in the browser.
- web browser — A program such as Chrome, Firefox or Safari that downloads web pages and turns their code into the screen you see and use.
- HTML — The markup language that describes the structure and meaning of a web page with elements such as <button>, <input> and <h2>.
- CSS — The language that describes how web pages look: colours, fonts, spacing, layout and animation.
- JavaScript — The programming language of web browsers, also widely used on servers through Node.js.
- full-stack development — Building every layer of a web application yourself: the browser frontend, the backend server and API, and the database behind them.
- Client Component — A component whose code is also sent to the browser so it can use state, effects and event handlers.
- full-stack — Covering both the frontend that users see and the backend servers and data behind it.
Taught in
- Polymorphism & Slotted Composition: The asChild Pattern — Design Systems & Component Engineering
- How Browsers Work: Navigation, DNS, TCP, TLS And Request Timing — Frontend Architecture & Web Platform
- Accessibility Tree, ARIA Roles, States And Live Regions — Frontend Architecture & Web Platform
- Advanced CSS Grid: Named Areas, minmax And auto-fit — Frontend Architecture & Web Platform
- Same-Origin Policy, CORS Preflight, Credentials And Headers — Frontend Architecture & Web Platform
- Monorepo Architecture: Workspaces & Turborepo — Production Full-Stack Engineering
- End-to-End Type Safety: Shared Schemas & DTOs — Production Full-Stack Engineering
- API Gateway & BFF Patterns: Backend-for-Frontend — Production Full-Stack Engineering
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- Instrumentation: OpenTelemetry & Performance Spans — Next.js 15 & Modern App Router Architecture
- React Fiber Architecture: Work Units, Priority And Commits — React 19 & Modern Component Architecture
- useImperativeHandle: Controlled Ref Forwarding Boundaries — React 19 & Modern Component Architecture
- Slot Patterns And Headless UI Architecture in React — React 19 & Modern Component Architecture
- Custom Hook Composition: Encapsulating Reactive Logic — React 19 & Modern Component Architecture
- Suspense Architecture: Promises, Fallbacks, And Co-ordination — React 19 & Modern Component Architecture
- Code-Splitting with React.lazy: Dynamic Imports And Chunks — React 19 & Modern Component Architecture
- The React Compiler: Automated Memoization Under The Hood — React 19 & Modern Component Architecture
- any Versus unknown: Defensive Typing In Practice — Production TypeScript
- Discriminated Unions: Tagged Variants And Pattern Matching — Production TypeScript
- Why Generics: Functions, Identities And Type Variables — Production TypeScript
- The satisfies Operator: Safe Validation Without Widening — Production TypeScript
- The Spine Artifact: Generating Typed Models From OpenAPI — Production TypeScript