liveBook · Manning

Single-page application

Also called SPA, single-page app

A single-page application is a web application that loads a document and dynamically updates its content or interface without full-page navigation for most interactions.

How 6 Manning books explain it

Build a Frontend Web Framework (From Scratch)

A web application that updates its displayed content and navigation within one initially loaded document rather than requesting a new page for each route.

How it is used
Frames route changes without page reloads as a way to understand frontend framework behavior.
How deep it goes
Walks through loading, mounting, and route updates, but does not provide a router implementation.
Examples
Illustrates Document API element creation with a “Hello, World!” paragraph and diagrams of loading, mounting, and navigation.
What you can do after
Evaluate/understand it by tracing how one loaded document becomes a view and changes when the route changes.

Read how Build a Frontend Web Framework (From Scratch) explains single-page application →

Django in Action

A single-page application is a web application that renders its interface and performs substantial application logic in the browser within a single web page.

How it is used
Positions SPAs as a browser-interface architecture backed by Django APIs, alongside server-rendered and mixed-page approaches.
How deep it goes
Explains browser-versus-server rendering, JavaScript bundles, JSON APIs, and Django API tooling without implementing an SPA.
Examples
Uses React, Angular, Vue.js, Django REST Framework, Django Ninja, and mobile frontends as concrete architecture examples.
What you can do after
Evaluate/understand whether a browser-rendered SPA, a server-rendered site, or a mixed interface fits a Django project.

Read how Django in Action explains single-page application →

Modern Angular

A single-page application is a web application that loads a single document and updates its displayed content through client-side code during navigation.

How it is used
Frames browser-rendered Angular applications as a fast-interaction architecture and contrasts their trade-offs with server-side rendering.
How deep it goes
Explains initial HTML, script loading, browser rendering, performance effects, and deployment fallback; defers server-specific configuration details.
Examples
Uses an HRMS application, its index.html and root component, and a direct /products request to illustrate SPA behavior.
What you can do after
Operate/configure SPA hosting by serving bundled assets and returning index.html for routes unknown to the server.

Read how Modern Angular explains single-page application →

Vanilla Web

A single-page application is a web application that updates its interface within one loaded document rather than performing full document loads for each view.

How it is used
Uses client-side routing to move between application views without reloading the page context.
How deep it goes
Explains the navigation model and server fallback behavior, without detailing a router implementation.
Examples
Uses a direct request to /products/42 and a deployment under /dashboard/ to expose routing configuration failures.
What you can do after
Operate/configure it by rewriting app routes to the entry document while preserving files, API endpoints, and genuine 404 responses.

Read how Vanilla Web explains single-page application →

ASP.NET Core in Action, 3e

A single-page application is a web application that updates its user interface dynamically without full-page navigation for most interactions.

How it is used
Explains browser applications that fetch server data and update their interfaces without full-page navigation.
How deep it goes
Describes initialization, JSON communication, and client-side HTML generation without detailing framework internals.
Examples
Uses Angular, React, Vue, Blazor WebAssembly, initial JavaScript files, and JSON responses as examples.
What you can do after
Evaluate/understand how browser applications load, communicate with servers, and generate updated interfaces.

Read how ASP.NET Core in Action, 3e explains single-page application →

React Quickly, Second Edition

A single-page application is a web application that dynamically updates its interface in the browser without full-page navigation for most interactions.

How it is used
Explains browser-centered websites whose functionality, rendering, validation, and UI changes happen largely on the client.
How deep it goes
Maps the request-to-render flow and contrasts thick and thin clients, but stops short of detailed implementation.
Examples
Uses Facebook, Google Docs, Gmail, button clicks, dragging, hovering, JSON, XML, and loading screens as examples.
What you can do after
Evaluate React's role in an SPA stack and distinguish a browser-heavy client from a thin client.

Read how React Quickly, Second Edition explains single-page application →

Also covered in

What to know first

Related concepts

Questions about single-page application

What is single-page application?

A single-page application is a web application that loads a document and dynamically updates its content or interface without full-page navigation for most interactions.

Which Manning books explain single-page application?

Build a Frontend Web Framework (From Scratch), Django in Action, Modern Angular, Vanilla Web, ASP.NET Core in Action, 3e and React Quickly, Second Edition.

What should I know before learning single-page application?

Manning books that teach single-page application usually introduce JavaScript, HTML, component and CSS first.

What is the difference between single-page application and multi-page app?

A single-page application is a web application that loads a document and dynamically updates its content or interface without full-page navigation for most interactions. A multi-page application is a web application whose navigation loads separate HTML documents for different routes or views.

What is single-page application a kind of?

Single-page application is a kind of web application. A web application is software that provides functionality through web technologies and is accessed over a network, typically through a browser or other web client.

What is single-page application also called?

Single-page application is also called SPA or single-page app.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.