Loading content
Single-page applications (SPAs) are web applications that load a single HTML page and dynamically update content using client-side JavaScript. They centralize routing and state in the browser to create fluid, app-like interactions. SPAs trade server-rendered simplicity for richer interactivity and require considerations for SEO, performance, and routing.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
A single-page application loads a web application as one document and then updates content dynamically in the browser.
SPAs were enabled by capable browser JavaScript environments and Ajax communication. They move navigation and parts of rendering from the server into the client.
The browser initially loads an application shell, then manages routing and UI state and fetches data asynchronously. This creates fluid transitions but requires deliberate state, error, loading, and accessibility design. SEO, first-load performance, deep links, and server-side rendering need explicit treatment. An SPA is a web UI interaction and delivery pattern, not a particular framework.
An initial document loads JavaScript and the application’s basic structure.
Routes and content change in the browser without loading a complete document for every view.
Interaction becomes direct, while first-load performance, SEO, accessibility, and state management become more demanding.
SPAs help evaluate web architecture for interactive applications. The choice should reflect users, network conditions, SEO, accessibility, and the operating model.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.