Service · Web development

Custom Single Page Application development.

A SPA is a web app that you load once, after which all navigation and interaction happens client-side — think Gmail, Trello, Notion or Figma. We build custom SPAs for dashboards, customer portals and SaaS products where an app-like feel and speed are decisive for the UX.

React & VueTypeScriptPWA-readyReal-time UI

A SPA is an app, not a website.

With a traditional website (multi-page application), every click requests a new HTML page from the server. With a Single Page Application, the browser loads a JavaScript bundle once, and after that the app handles all navigation, data exchange and state itself. For the user it feels like a desktop or mobile app: instant transitions, no flash of white, and the sense that everything responds immediately. Classic examples you use every day are Gmail, Google Maps, Trello, Notion and Figma — all SPAs.

That makes a SPA the right choice for products where users spend longer sessions — dashboards, project management tools, customer portals, configurators and real-time applications. For a marketing site or content platform, a SPA is usually not the best idea, and we are upfront about that. We weigh up a SPA, a server-rendered MPA or a hybrid approach with islands (Astro) together with you, before a single line of code is written.

We have been building SPAs for years for SaaS vendors, B2B portals, admin panels and mobile-first web apps. Always custom, always with TypeScript from start to finish, and always with attention to the areas where SPAs are traditionally weak: fast initial load, accessibility and behaviour on poor connections. How a SPA fits into the broader range of web development is something we are happy to discuss in an introductory meeting.

Three typical SPA projects.

Most SPA requests we see fall into one of three patterns. Which one fits depends on the type of product and the degree of real-time interaction. We advise on this in the first conversation.

Compact project · fixed sprint budget

Customer portal or dashboard app

A logged-in environment where users view data, check reports and carry out actions. React or Vue 3 on the front end, a REST or GraphQL API underneath, and a component library such as shadcn/ui or Radix UI for the UI building blocks. Suitable for B2B portals, vendor dashboards and in-house admin tooling.

React + ViteTanStack QueryJWT authREST API
Mid-sized project · fixed sprint budget

SaaS product with multiple modules

A full-fledged product with multiple roles, an extensive data model and well-considered UX flows. Think of a planning app, a Trello-like board, or a vertical SaaS for a specific industry. A modular front end, type safety from database to UI, and a design system that grows with the product.

TypeScriptZustand or ReduxtRPC or GraphQLAuth0 or Keycloak
Larger project · fixed sprint budget

Real-time or PWA application

A SPA in which live updates, collaboration or offline flow are central: a chat platform, a monitoring cockpit, a trading environment or a field app that has to keep working without internet. WebSocket or Server-Sent Events for the stream, service workers for the PWA layer, and installable on both desktop and mobile.

WebSocketService workersInstallableOffline-first

The technology choices we make.

A SPA is more than just a framework. Each of these choices affects development speed, maintainability and how well your team can still maintain the app in a few years' time. A short tour of what we typically use and why.

Framework

React, Vue, Angular or Svelte

React with Vite or Next.js is the stack we choose most often: the largest ecosystem and the easiest to scale a team around. Vue 3 with the Composition API and Nuxt is a good alternative, especially for teams with a Vue background. We pick Angular for enterprise projects where strict TypeScript is central. Svelte or Solid.js for lightweight or performance-critical apps.

State management

Zustand, Redux or TanStack Query

For most apps we start with TanStack Query for server state plus Zustand for local UI state: simple and scalable. We reserve Redux Toolkit for complex domains where time-travel debugging genuinely adds value. In Vue projects, Pinia is the standard. We avoid state spaghetti by setting clear conventions from sprint one.

Forms and validation

React Hook Form, Formkit

Forms are where many SPAs get stuck: validation rules that drift out of sync with the backend, poor error states, inaccessible labels. We work with React Hook Form and Zod schemas shared between client and server, so a single source of truth governs validation. In Vue we use Formkit with the same pattern.

Auth layer

Auth0, Keycloak or custom JWT

For customer portals, we often choose Auth0 or a comparable hosted IdP: quick to go live, social logins included for free, and SAML and SSO as you grow. For privacy-sensitive sectors or on-premise requirements, we use Keycloak, which you can host yourself. We only build a custom JWT stack if the requirements are truly unique, because authentication mistakes are expensive.

Backend and data

REST, GraphQL or tRPC

An SPA is only as good as the API beneath it. We build REST with Spring Boot, Node or Django; GraphQL with Apollo or Hasura when the data model is relational and the UI needs many different slices; and tRPC when client and server both run on TypeScript and we want end-to-end type safety without schema generation.

Real-time

WebSocket, SSE or Phoenix

For chat, multi-user collaboration and live dashboards we use WebSockets (via Socket.IO or a managed service such as Pusher or Ably). We choose Server-Sent Events when the stream is one-way, as it is simpler to scale. For Elixir/Phoenix backends we use Phoenix Channels, which are built for exactly this kind of real-time UI.

What you get at the end.

A production-ready SPA, plus everything around it so you can manage it yourself, extend it, or hand it over to another team. No black box.

  • The SPA in production + stagingTwo environments, running in your cloud (GCP, AWS, Azure) or with us. A CI/CD pipeline is ready for further development.
  • Codebase and design systemFull TypeScript source, build instructions, a documented component library, and Storybook or a comparable component catalogue.
  • API layer and data contractsThe backend endpoints the SPA relies on, with an OpenAPI or GraphQL schema and a typed client so front end and back end never drift out of sync.
  • Test suite and performance budgetUnit tests, end-to-end tests in Playwright or Cypress, and clear Core Web Vitals targets that we check with every release.
  • Maintenance contract (optional)Monitoring, security patches for dependencies, performance monitoring and further development. Fixed monthly price, four response-time tiers.

When an SPA is the right choice.

Four patterns where a Single Page Application genuinely adds value. If you recognise your situation here, we'd be happy to talk further.

App feel

Logged in, for longer than a minute

Your users don't stay for five seconds; they work in the tool. A full-page reload on every click breaks that rhythm. An SPA feels the way a desktop or mobile app does.

Real-time

Data changes during use

A dashboard with live KPIs, a chat, a trading screen, a monitoring cockpit. SPAs with WebSocket or Server-Sent Events show updates without the user having to hunt for a refresh button.

Complex state

Many interactive screens

Filters, drag-and-drop, multi-step forms, nested tables, in-place editing. This kind of UI calls for client-side state management, and that is what SPAs are built for.

PWA ambition

Installable and offline-capable

A field engineer with no 4G in a basement. A tablet app for the shop floor. PWA functionality on top of an SPA gives you home-screen installation plus a workable offline mode.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How an SPA project works with us.

1

Introduction and scoping

A conversation in which we work out which flows the SPA needs to support, what type of users will work with it, and where it integrates with your existing landscape. Here we often also compare an SPA with a server-rendered alternative — not everything needs to be an SPA.

2

Tech choices and UX workshop

Together we decide on the framework (React, Vue, or sometimes Svelte), the state approach, the auth layer and the backend strategy. In parallel, we work out the first screen flow in Figma with you and a few end users, so the build starts from a design everyone supports.

3

Building in sprints

A working build every two weeks that you can test. We build in vertical slices: first a working end-to-end flow with a single role, then more depth, then additional roles. Performance budget and accessibility checks run from sprint one.

4

Hardening and rollout

Penetration test, accessibility audit (WCAG 2.2 AA), Lighthouse report, and a phased rollout to your users. After that, we can handle maintenance, or hand over cleanly to your own team with a runbook and a few handover sessions.

SPA versus the alternatives.

An SPA is not automatically the right choice. Below are the three most common alternatives and when they are a better fit. We discuss this honestly in the first conversation — if an SPA doesn't fit, we'll say so.

Traditional MPA

Server-rendered multi-page

A classic server-rendered website built with Rails, Django, Laravel or Spring. Better for content-heavy sites, marketing pages and publications that need to rank highly in search engines. No client-side JavaScript requirement, fast first paint, straightforward SEO. We use this for your public website and choose an SPA for the logged-in tooling behind it.

MPA with islands

Astro or a hybrid approach

Astro renders server-side by default, but lets you add "islands" where interactivity is needed. That way you combine the SEO performance of server rendering with the interactivity of React or Vue in specific places. A good compromise for sites that are partly content, partly app — for example, a marketplace with product pages plus a logged-in dashboard.

Native or hybrid app

iOS, Android or React Native

If you need deep hardware access (camera, Bluetooth, push notifications on iOS), a genuine offline flow over long periods, or App Store distribution for consumer reach, a native or hybrid app is often the better choice. We advise on these and build them too, but for many use cases a PWA built on an SPA is a cheaper, faster route to the same result.

No-code platforms

Bubble, Retool, Webflow

For internal tools or an initial validation, no-code platforms can quickly give you something that works. It runs into trouble when you need your own branding, complex roles, real-time functionality or custom integrations — you quickly end up with a lock-in that is expensive to unwind later. We often advise: start with no-code for the initial validation, then move to a custom SPA once the product proves itself.

Frequently asked questions.

The questions clients ask before we start an SPA project.

What is the difference between an SPA and a multi-page application?
In a multi-page application (MPA), the server sends a new HTML page with every click. In a Single Page Application, the browser loads a single bundle, and JavaScript then handles all navigation and data exchange. SPAs feel fast and app-like after the initial load, while MPAs render faster on first paint and suit content-heavy sites better. For admin panels, SaaS and dashboards, an SPA is almost always the right choice; for a marketing site or news platform, it usually isn't. Hybrid approaches such as Astro with islands also exist, and we're happy to discuss them if your product would benefit.
What about SEO with a Single Page Application?
SEO for SPAs has been far less of a problem since 2018, as Googlebot now executes JavaScript. For public pages that need to rank highly, though, we often still recommend a hybrid approach: server-side rendering or pre-rendering with Next.js, Nuxt or Remix, so that the first paint is indexable. For logged-in dashboards and internal tools, SEO plays no role at all, so we opt for pure client-side rendering because it keeps the architecture simpler. We make that decision per page type, not for the whole app.
Do you choose React, Vue or Angular?
We work with React most, because its ecosystem is large and it makes it easy to find team members or another development partner later. We're happy to use Vue 3 if your own team already has a Vue background or if you want Nuxt for SSR. In our experience, Angular is mainly relevant in enterprise environments where strict TypeScript and a tightly structured framework are required. We use Svelte and Solid.js occasionally, when the use case calls for it. We don't choose based on hype, but on your team and on what you still want to be maintaining in five years.
Can the SPA be installed as an app on a phone or laptop?
Yes, that's exactly what Progressive Web App functionality adds. With service workers, a web manifest and the right icons, your SPA becomes installable via the browser, without having to go through the App Store or Play Store. It works on desktop, Android and iOS. PWAs are a good alternative to a native app when you don't need deep hardware access and don't want to maintain separate iOS and Android codebases. For heavy offline use or camera and Bluetooth features, we also look beyond PWAs to a true native or hybrid app.
How do you handle real-time updates in an SPA?
It depends on the pattern: for two-way communication such as chat and multi-user collaboration, we use WebSockets, usually via a library such as Socket.IO or a hosted service such as Pusher or Ably. For one-way updates such as a live dashboard, we often choose Server-Sent Events, as they are easier to scale. For optimistic UI updates and cache synchronisation, we use TanStack Query or similar tooling. The guiding principle is always that the UI responds immediately, even if the server answers a little later.
What determines the cost of an SPA project?
The number and complexity of the screens, the number of roles and permissions, the depth of the integrations with your existing systems, and the degree of real-time or offline functionality. A logged-in portal for a single role with a handful of views is a different conversation from a SaaS platform with ten roles, three integrations and a PWA layer. We work with fixed sprint budgets, so you stay in control of spending sprint by sprint. In the first conversation, we sketch out the scope together and give you an honest indication.
How long will it take before we can go live?
A first working version of a well-defined portal or dashboard can be live within a few sprints. A full SaaS product with multiple modules and integrations is a multi-sprint project, with a phased rollout to your users. We deliberately avoid promising a fixed number that would do violence to the scope — but we do commit to a sprint cadence and clear milestones, so you can adjust course at any point.
Do you work alongside our own developers?
Yes, we often do. Some clients want us to build the SPA entirely and then take over its maintenance; others want co-development from day one so their own team can take over the codebase later. We're productive in both setups, as long as we agree upfront on code ownership, review protocols and the handover. A well-documented design system makes that handover far easier.

Talk to us about your Single Page Application.

A no-obligation introductory call of half an hour. We listen to what you want to build, think along with you on the tech choices, and tell you honestly if an SPA isn't the best fit for your problem. We're also happy to advise on questions around microservices architecture or a broader enterprise software strategy.

Edit content