SPA

A Single Page Application (SPA) is a web application that loads once and then rewrites its own interface in the browser, using JavaScript to fetch data and update the view instead of asking the server for a new page on every click. The pattern rose with frameworks like Angular, Ember, React, and Vue, and it is one of the clearest architectural reasons APIs matter — the SPA is just a shell, and the API is where the actual work happens.

• Client-side rendering - The browser owns the UI, assembling and updating the page from data rather than from server-rendered HTML.
• API-driven state - Every meaningful interaction becomes an HTTP call to a backend API, making the API contract the real product.
• Decoupled front and back end - The same API can serve a web SPA, a mobile app, and a partner integration without change, encouraging clean separation.
• Rich, app-like experience - Navigation, forms, and updates happen without full reloads, which is why SPAs feel closer to native software.

In my work an SPA is often the first honest test of an API’s design, because the moment a team builds a real front end against their own API they discover the gaps, chattiness, and missing endpoints that documentation alone hides. This is why I have long pointed to the SPA as a forcing function for good API design — it pushes teams toward well-specified contracts described in OpenAPI, and it foreshadows today’s agentic turn, where an AI agent consumes those same APIs the way a browser-based SPA always has.