IT Glossary
What is a Single-Page Application?
A web application that loads once and then flows — every subsequent click is instant, with no page reloads. Gmail is the archetype.
Compare two experiences in a browser. On a classic website, every click reloads the entire page — a brief white flash, everything redrawn. In Gmail, you move between messages, search and archive with nothing reloading; it flows like installed software. The second is a single-page application: the browser downloads the application once (code and interface), and from then on only data travels — clicks change content locally and instantly, with discreet API calls to the server. This is the natural architecture of modern business tools — dashboards, web ERPs and CRMs, customer portals, internal apps — built with the frameworks dominating the market (React, Vue, Angular). Three nuances deserve a buyer's attention because they surface in real decisions. Search visibility: a pure SPA indexes poorly since content is born in the browser, which is why the practical rule splits the world — apps behind a login are SPA territory, while public pages that must rank need server-side rendering, handled elegantly by hybrid frameworks like Next.js. First load: the SPA pays at the door what it saves later, so optimisation discipline is not optional on mobile. And security: everything running in the browser is visible and modifiable by the user, so validation in the interface is comfort, never defence — the server keeps the last word.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
An app experience, not a site experience
Instant navigation, preserved state, fluid interactions — users work without the frustration of reloads at every step.
A lighter server and a reusable API
The server delivers data rather than whole pages — the same API feeds the web app, the mobile app and future integrations.
The natural home of business tools
Dashboards, portals, web ERPs — interaction-heavy workloads get the architecture modern frameworks were designed around.
Frequently asked questions
SPA or a classic website for our project?
Decide by nature: an interactive application behind a login (portal, dashboard, internal tool) is SPA territory without hesitation; a public site that must be found on Google (company site, blog, e-commerce) needs server-side rendering — ideally a hybrid framework like Next.js or Nuxt that gives both indexability and fluidity. A vendor who asks unprompted 'what needs to be indexed?' is showing competence.
Is it true SPAs have problems with Google?
A pure SPA does — content born in the browser indexes late and imperfectly — but the fixes have been standard for a decade: server-side rendering, static generation of public pages, hybrid frameworks doing both by default. Avoid the naive implementation, not the architecture; an app behind a login has no such problem because search engines never enter.
The first load feels slow on mobile — is that normal?
It is the architecture's entry cost, but 'slow' signals missing optimisation rather than fate: code splitting, compression, lazy loading and size budgets keep first load civilised even on 4G. At acceptance, the test is concrete — first open on a mid-range phone over a mobile connection, timed, with a Lighthouse report putting numbers on it. After that first load, the SPA takes its revenge: everything is instant.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247