Skip to content

What a Single-Page App Actually Is

A single-page application loads once in the browser and then updates the screen in place as you use it, instead of fetching a brand-new page from the server every time you click. The page never fully reloads — it rewrites parts of itself, fast and smooth, like a desktop app living in your browser tab.

That’s the appeal in one line: it feels slick and immediate, because it isn’t going back to the server for a fresh page on every interaction. Gmail, Trello, a live dashboard — those feel responsive because they’re SPAs. The technology is genuinely good. The problem is where it gets used.

When a single-page app actually matters

It matters when you’re building something that’s genuinely an application — where the user stays a long time, does a lot of interactive work, and the experience needs to feel like software rather than a document.

A dashboard people live in all day. An editor. A tool with constant state changing on screen — drag-and-drop, live updates, complex forms that react as you fill them. For those, the SPA earns its complexity, because the alternative (reloading the whole page on every action) would feel clunky and slow. When the product is an interactive app, build it like one.

That’s a real but narrow set of cases. And the narrowness is the point of this page.

When it’s the wrong tool — which is more often than it’s used

Here’s the honest part most explanations skip: the SPA is reached for constantly when a plain, server-rendered website would be simpler, faster, and better. It’s become a default for projects that have no business being one.

A marketing site, a blog, a brochure, a content site, most of an e-commerce shop — these are documents, not applications. Someone reads a page, maybe clicks to another. They don’t need a JavaScript framework booting up in their browser to do that. When you build a content site as an SPA, you usually buy yourself a pile of problems for no benefit: a slower first load while a heavy bundle downloads, worse SEO unless you do extra work to fix what you broke, more moving parts, more that can fail, and a build that needs a specialist to touch. You took something the browser does brilliantly for free — loading pages — and reimplemented it, worse, in JavaScript.

This is the simplicity principle in its purest form. The simplest thing that solves the real problem wins. For most websites, that’s server-rendered pages, and reaching for an SPA is solving the impressive-looking problem instead of the real one. I’ve been called in more than once to fix a site that was slow and unmaintainable specifically because someone built a content site as an SPA when it never needed to be. The fix is usually to take the framework back out.

How to tell which you’ve got

One test cuts through it: does the user mostly read, or mostly do? If they mostly read and navigate — it’s a site, render it on the server, keep it simple and fast. If they mostly do — sustained, interactive work with state changing constantly — it’s an app, and the SPA earns its keep. Most things people want to build are sites with a few interactive corners, and the right answer there is a server-rendered site with interactivity dropped in only where it’s needed, not an SPA wrapped around the whole thing.

Where to go next

I explain this one plainly because “we’ll build it as a single-page app” gets said reflexively, and it’s one of the more expensive reflexes in modern web work. It leans heavily on APIs — an SPA is constantly fetching its data through them — and connects to technical debt, since an SPA built where it wasn’t needed is a textbook case of complexity you’ll service for years.

If someone’s quoting you an SPA and you can’t tell whether you need one, that’s exactly the kind of call worth a second opinion. Tell me what you’re building and I’ll tell you whether it wants to be an app or just a fast, simple site.