Service · Web development

Custom React JS website development.

Custom websites and web applications on the modern React stack — SPA, SSR or SSG, with React 18+, Next.js, TanStack and shadcn/ui. For customer portals, dashboards, e-commerce frontends, marketplaces and brand experiences where UI state and component discipline make the difference.

React 18+TypeScriptNext.js / RSCshadcn/ui

React JS is not a framework — it is the foundation on which you choose.

React is Meta's open-source UI library, which has reshaped the way the web is built since 2013. Components instead of templates, declarative state instead of DOM manipulation. Today's choice is no longer about whether to use React, but about which React context: a classic single-page application, a Next.js app with server components, or an Astro site with React as an island.

For business websites and web applications, React is almost always the pragmatic default once the interface goes beyond content pages. Dashboards, customer portals, e-commerce frontends, marketplaces, configurators and design-system-driven brand sites: anything where UI state, form flows or dynamic data are the centre of gravity sits right at the heart of what React does.

We build React projects for clients who want custom software without tying themselves to a closed platform. The broader service context is on web development; for SPA projects see building a single-page application and for capacity see hiring a React developer. On this page you can read when React fits, when another framework is the more honest choice, which stack we start with and how a project runs.

When React JS is the right choice.

Five patterns in which React-built websites and web applications consistently pay for themselves. If you recognise one of them, React belongs on your shortlist.

Customer portals & dashboards

Lots of UI state, few content pages

A portal where users filter data, sort tables, fill in forms and see real-time status updates. This is where React comes into its own: TanStack Query for server state, Zustand or Redux Toolkit for client state, React Hook Form for forms and TanStack Table for data tables. No template engine that gives up halfway, but one consistent component model used throughout the entire app.

E-commerce frontends

Headless commerce on a fast React layer

For headless setups on Shopify, BigCommerce, commercetools or Magento, React with Next.js is the standard. Product pages via incremental static regeneration or partial pre-rendering, cart and checkout as client components, and server actions for mutations. The result is a fast storefront that search engines love and that your merchandising team can steer through its own design system.

Marketplaces & SaaS extensions

Products that keep growing over time

Marketplaces, multi-tenant SaaS applications and internal tooling that grow with the company. Here a component library shared across the whole organisation pays off, via design tokens, a UI package and API clients generated from OpenAPI or GraphQL. For the backend we often work with Laravel, Node or a Python API.

Design-system-driven brand experiences

Brands that run their own design system

For brands that want to consolidate their digital presence into a single design system, running web, mobile and internal tools from it, React is a natural pivot. Components in Storybook, design tokens in a shared package and code sharing with the mobile app via React Native. One source, multiple channels.

Real-time & collaborative UI

WebSockets, optimistic updates, presence

Apps where multiple users work in the same view at the same time: planning boards, editors, dashboards with live data. React's reconciliation model and hooks architecture make tracking presence, optimistic updates and server pushes orderly rather than exhausting. We add Liveblocks, Partykit, Pusher or a custom WebSocket layer where it fits.

Migrating from a legacy stack

From jQuery, AngularJS or legacy PHP frontends

You have a working site or app on a stack that is no longer maintained: AngularJS, jQuery with server templates, an old Vue 1 or Ember installation. We migrate in phases: new screens in React, while the existing environment keeps working via a micro-frontend boundary. No big-bang rewrite.

When React JS isn't the right choice.

Being honest saves you an expensive rethink halfway through. These are three patterns in which we point clients towards a different framework or a simpler stack.

Not 01

Content sites without serious dynamics

For brand websites, magazines, marketing pages or company sites with little interactivity, React is often too heavy. Astro or Eleventy delivers the same editorial flexibility with considerably less JavaScript in the browser, better Core Web Vitals out of the box and a simpler editing workflow. Astro can also run React components as islands, so you can happily start with Astro and use individual React islands where interaction makes sense.

Not 02

Microsites and simple campaign pages

A temporary campaign site, a product launch page or a ten-page microsite doesn't need to be a full React project. The TTFB gains, editorial speed and cost control of a static generator (Astro, Eleventy, Hugo) are usually better for these projects. Add React when you need an interactive widget, not as the default.

Not 03

Back-office tooling that's finished faster in Laravel

For internal CRUD applications, admin panels and back-office tooling, a Laravel stack with Filament or Livewire can get you to production faster than a separate React frontend on top of an API. You save on the auth layer, the API contracts and the duplicated state. We choose this route where the feature set is driven primarily by database fields rather than rich client-side interaction, and we discuss it openly in the first conversation.

React versus Vue, Svelte and Angular: a sober comparison.

The four mainstream options side by side, for anyone still choosing or wanting a second opinion. If you're unsure, we guide the choice in the first conversation, based on your existing stack, team and product ambitions.

Criterion
React
Vue 3
Svelte / SvelteKit
Angular
Language & mental model
JSX, hooks, functional
SFC template, composition API
Compiler-first, minimal runtime
Heavy on TypeScript, RxJS, OOP
Dutch talent pool
Very large, the default choice
Large, mainly creative agencies
Small, growing slowly
Large, mainly enterprise
Ecosystem & libraries
The broadest, everything is there
Robust, often parallel to React
Younger, high quality
Complete but closed
Server-side / meta-framework
Next.js, Remix, Astro+React
Nuxt 3
SvelteKit
Angular Universal
Bundle size
Larger, RSC reduces it
Small, comparable to React
Very small, the compiler strips out a lot
Large, a full framework
Learning curve
Hooks take practice
Easy to get started
Quick to become productive
Steeper, with many concepts
Code sharing with mobile
High via React Native
Limited, no native counterpart
No native counterpart
NativeScript route, niche
Best for
Portals, dashboards, SaaS, headless commerce
Content-heavy sites, agencies
Performance-critical apps, embeddable widgets
Large enterprise monoliths

The modern React stack in 2026.

Our default configuration for production-grade websites and web applications. Depending on your scope we swap out components, but these are the building blocks we start with as standard.

Core & framework

React 18+, Next.js 14+ App Router, RSC

We start on a recent React release with the Next.js App Router and React Server Components by default where they fit. Server components render as much as possible on the server so the bundle sent to the browser stays small, while client components only run where interaction is needed. For projects without an SSR aspect we choose Vite with react-router or TanStack Router, which is lighter and faster than a full Next.js setup when you don't need one.

TypeScript & validation

Strict TypeScript, Zod, generated types

Every React codebase we build is TypeScript-only, with strict mode on and no `any` escape hatches. API contracts become type-safe: for REST we generate types from OpenAPI, for GraphQL we use GraphQL Code Generator. On the input side, we validate runtime data with Zod, both forms and external payloads, so the boundary between "what the compiler knows" and "what the browser receives" is explicit.

Data & state

TanStack Query, Zustand, Redux Toolkit

TanStack Query is our default for server state, with caching, refetching, optimistic updates and mutation handling in one consistent model. For client state we choose Zustand in most cases, and Redux Toolkit only when the complexity genuinely calls for Redux DevTools and time-travel debugging. Global UI state (modals, toasts, theme) runs on a thin Zustand store.

UI & design system

Tailwind, shadcn/ui, Radix Primitives

Tailwind CSS for utility-first styling, tied to design tokens from your brand identity. shadcn/ui provides accessible, copyable components on top of Radix primitives. Instead of a closed component library, you copy the components into your own codebase and adapt them. For clients with a strong brand, we build on this and publish an internal UI package via Storybook with visual regression tests.

Forms & tables

React Hook Form, TanStack Table

React Hook Form for high-performance forms with minimal re-renders and Zod validation on both sides. TanStack Table for data grids: it's headless, so styling stays entirely in your hands, while sorting, filtering, pagination, virtualisation and column pinning come ready-made. For form-heavy portals, this combination saves sprints of boilerplate that would otherwise be written by hand.

Routing & data loading

Next.js routes, TanStack Router, Server Actions

For Next.js projects we use the App Router with file-based routing, layouts and parallel routes. Data loading happens via async server components, or via Server Actions for mutations, with streaming SSR where it improves TTFB. For pure SPAs we choose TanStack Router: type-safe routes, a loader API that pairs well with TanStack Query, and search-param validation with Zod.

Testing & quality

Vitest, Playwright, Testing Library

Vitest for unit and integration tests, React Testing Library for components and Playwright for end-to-end flows on real browsers. Storybook with Chromatic or Playwright snapshots for visual regression. Accessibility is built in from the start, through axe-core in CI, semantic roles, focus management and contrast checks against WCAG 2.2 AA, rather than as a separate phase at the end.

Hosting & edge

Vercel, Netlify, Cloudflare, your own Node

Vercel is the most comfortable route for Next.js, with preview deployments per PR, edge rendering and automatic cache invalidation. Cloudflare Pages and Workers for edge-first scenarios or if you're already on the Cloudflare stack. Netlify for Astro + React projects. When compliance or cost requires it, we run Next.js in standalone mode on your own Node server in your VPC on AWS, GCP or Azure, so you're not locked in to a single vendor.

Monitoring & analytics

Sentry, Vercel Analytics, PostHog

Sentry for JavaScript errors and performance traces, with source maps and release tracking. Web Vitals via Vercel Analytics or a privacy-friendly alternative. PostHog for funnels, feature flags and phased rollouts. Feature flags are part of the architecture from day one.

CI/CD & security

GitHub Actions, Dependabot, OWASP checks

GitHub Actions for pull request checks (lint, type check, tests, build) and preview deployments. Dependabot or Renovate for dependency updates, plus OWASP dependency check and npm audit in CI. For authentication we choose NextAuth/Auth.js, Clerk or a custom OIDC integration with your IdP.

Three flavours of React projects.

It depends on where you are now and what it needs to deliver. We'll advise which approach fits in the first conversation — no fixed packages, but clear outlines.

SPA project · fixed sprint budget

Customer portal or dashboard as a single-page app

An interactive portal or dashboard without public SEO pressure: TanStack Router, TanStack Query, shadcn/ui and your own design token set. Authentication via SSO or magic link, a fine-grained role model and an API layer that we build ourselves where needed. The broader SPA context is covered on custom single-page application development.

Vite + ReactTanStack RouterSSOshadcn/ui
Next.js project · fixed sprint budget

Public website or webshop with SSR and RSC

Next.js with the App Router and server components for public pages that search engines and users need to be able to open quickly. Headless CMS of your choice (Sanity, Strapi, Storyblok), e-commerce integrations via Shopify, BigCommerce or commercetools, and server actions for mutations. Edge rendering, ISR and partial pre-rendering where they improve TTFB.

Next.js App RouterRSCHeadless CMSVercel or your own Node
Design system project · fixed sprint budget

Own component library + monorepo for multiple channels

A shared React component package for your website, customer portal and, if needed, React Native app. Design tokens via Style Dictionary, Storybook as a living style guide, visual regression tests and generated API clients in a monorepo (Turborepo or Nx). For brands that want to consolidate their digital presence into a single source.

MonorepoStorybookDesign tokensVisual regression
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 →

What you get at the end.

A production-grade React codebase, plus everything around it to manage and keep developing the site or web application yourself. No vendor lock-in, no hidden licences, no inaccessible configuration.

  • The live applicationProduction and staging environments on your own Vercel, Netlify, Cloudflare or cloud account. You are the legal and operational owner of the runtime.
  • Codebase, TypeScript-only and testedFull source in your own GitHub organisation, strict TypeScript, lint and format config, unit and e2e tests, and GitHub Actions for PR checks and deployments.
  • Design system & StorybookComponents documented in Storybook, design tokens as a shared package, and visual regression tests. Usable by your own developers and designers without us as a bottleneck.
  • Documentation and ADRsBuild instructions, deployment runbook, Architecture Decision Records and an overview of all third-party services with roles and costs.
  • Monitoring from day oneSentry for errors and performance traces, Web Vitals, log pipeline and uptime checks. Including alerting config for the first week.
  • Handover to your teamTwo knowledge-transfer sessions, an architecture walkthrough and pair programming with the developers who will maintain the codebase. Accessibility report where EN 301 549 or WCAG 2.2 AA is required.
  • Maintenance contract (optional)Ongoing monitoring, dependency updates, security patches, performance tuning and further development. Fixed monthly price with clear response-time levels per ticket priority.

How a React project works.

1

Introduction and scoping

A conversation in which we understand what you want to build, for whom and which stack it fits. We assess whether React is the right answer for your case — and tell you honestly when Astro, Vue or a Laravel back office would be faster or a better fit. By the end of the conversation you'll have a direction, an initial scope outline and an idea of the project.

2

Architecture and design sprint

We draw up a sprint plan, sketch the architecture, choose the specific parts of the stack (Next.js or Vite, headless CMS, hosting, auth) and, where it makes sense, run a short design sprint for the key screens. For production apps, a spike on the most performance-critical screen or the hardest integration runs in parallel, so the assumptions are validated up front.

3

Building in sprints

Every sprint delivers a working preview deployment for each pull request. You test along with us, stakeholders do too, and feedback is incorporated incrementally. Core flows first, edge cases later. Code reviews, automated tests, accessibility checks and performance budgets are part of the cycle, not something done once at the end.

4

Hardening and go-live

Before go-live we run a dedicated hardening sprint: load tests, Lighthouse audits, a security scan, a pen test where relevant and a DNS cutover plan. For public sites we set up redirects from the old URL structure and a new XML sitemap.

5

Management and further development

After launch, the team keeps monitoring sharp, works through the first feedback and makes sure dependencies keep up. Further development runs in new sprints, prioritised on data and user feedback. Your team can take over parts whenever they're ready, with no lock-in.

Who we build React websites and web applications for.

Four types of organisation where our way of working with React has proven its value.

Product organisations

SaaS frontends and customer portals

You have a product with a growing user base and an API you maintain yourself. We build the web app your customers use, including dashboard, settings, SSO, roles and organisation management, and make sure your team can keep developing it.

Scale-ups

Headless commerce and marketplaces

You're outgrowing what a Shopify theme or a Magento frontend can handle and want to own the storefront. Next.js for the public side, a separate React app for admin, and a team that understands performance and SEO.

Enterprises

Modernising legacy frontends

An outdated AngularJS, jQuery or legacy PHP frontend that is no longer safe to develop further. We migrate to React in phases, with clear knowledge transfer. For extra capacity, you can also hire a React developer.

Agencies & brands

Design-system-driven brand experiences

For brands consolidating their digital presence into a single design system that powers the website, customer portal and, if needed, a mobile app. We deliver the React implementation and the Storybook documentation. You stay in control of brand and channels.

Fabian van Dijk Business developer · Appfront

First point of contact for React JS projects at Appfront. Reach out at fabian.vandijk@appfront.nl for a no-obligation introduction on whether React JS fits your stack, and when Astro, Vue or a Laravel back office is the honest answer.

Frequently asked questions about React JS.

What clients usually want to know before we start.

React or Next.js: what's the difference in practice?
React is the UI library; Next.js is a meta-framework that adds routing, server rendering, server actions and image optimisation on top of React. For public sites where SEO matters, we choose Next.js (App Router, React Server Components). For private apps such as customer portals and dashboards, we often choose a lighter Vite setup with TanStack Router.
Next.js or Astro with React islands: when to use which?
We choose Astro with React islands for content-heavy sites where most pages can be static, with React only where interaction is needed, such as a filter widget or a configurator. We choose Next.js when the whole product is a React app with dynamic data and complex routing. Astro with React often works well for marketing sites with a separate portal.
React Server Components: do you use them by default?
Wherever the Next.js App Router is used: yes. Server components shift work from the browser to the server, shrink the JS bundle and make data fetching more orderly. We reserve client components for what is truly interactive, such as forms, toggles, charts and drag-and-drop. For some existing Next.js codebases, the Pages Router remains the pragmatic choice.
How do you choose between Zustand, Redux Toolkit and React Context?
Default: TanStack Query for server state, Zustand for lightweight client state, and React Context only for dependency injection of services and themes. We choose Redux Toolkit when complexity reaches the point where Redux DevTools and time-travel debugging are worth it — rarely, in practice. For forms, React Hook Form is the right layer.
Do you work with a design system or build one?
Either. If you have a design system in Figma with tokens and components, we implement it via a Tailwind config and shadcn/ui. If you have nothing yet, we set up a minimal design system with tokens and a component library in Storybook. For brands that serve multiple channels, we build a shared monorepo package used by the web app, customer portal and, if needed, React Native.
How do you handle authentication and SSO?
Depending on your requirements, we choose NextAuth/Auth.js for Next.js projects, Clerk for a quick out-of-the-box route, or a custom OIDC or SAML integration with your IdP (Azure AD, Google Workspace, Auth0, Keycloak). For B2B portals, we work with a roles and organisation model. Session management happens server-side wherever possible — no tokens in localStorage.
What about SEO — is React a problem for search engines?
Not with SSR or static generation. For public sites, we always choose Next.js with SSR/SSG or Astro+React with islands. For private portals that shouldn't be indexed, SEO doesn't matter and a lighter Vite SPA works perfectly well. We deliver as standard with structured data, canonical URLs and sitemaps.
How do you approach performance and Core Web Vitals?
Server-render what you can, client-render what you must. RSC to reduce the bundle size, code splitting per route, image optimisation via Next/Image, font loading via subsetting and font-display swap. Lighthouse budgets in CI, and Web Vitals via Real User Monitoring in production. For heavy tables, virtualisation via TanStack Virtual.
What about accessibility?
WCAG 2.2 AA is the target, with semantic roles via Radix primitives, focus management for modals and menus, keyboard navigation tested as standard, screen-reader tests with VoiceOver and NVDA, and contrast checks and axe-core in CI. For projects subject to EN 301 549, we deliver an accessibility report listing known issues and mitigations.
Which backend do you pair with React most often?
Three routes. Laravel for clients with PHP expertise or who want a rich admin panel with Filament. Node.js (NestJS, Hono, Fastify) for full-TypeScript stacks where code and types are shared between frontend and backend. Python (FastAPI, Django) for ML- or data-heavy applications.
Vendor lock-in — will we end up stuck with Vercel?
No. Next.js runs in standalone mode on your own Node server in your VPC at AWS, GCP or Azure. Edge functions can also run on Cloudflare Workers. We deliberately keep the database, queues and object storage off Vercel where that fits your compliance requirements. Vercel is a convenience, not a requirement.
Can you review our existing React codebase?
Yes. We carry out a focused code review covering architecture, performance, accessibility and security, and deliver a written report with priorities — quick wins, mid-term work and strategic decisions. For longer-term capacity needs after that, you can hire a React developer to work alongside your team.

Talk to us about your React JS project.

A no-obligation introductory call of half an hour. We listen to what you want to build, look at how it fits into your existing stack and team, and give honest advice (React, Vue, Astro or something completely different) rather than automatically selling our own work.

If you want search engines to read the content of your React site unambiguously, look into structured data in JSON-LD.

Edit content