Service · Web development

Custom Vue website development.

Custom websites and web applications built on Vue 3 with the Composition API, Nuxt for SSR and SSG, and Pinia for state. For product teams who want to iterate quickly, for customer portals, dashboards and e-commerce, and for Dutch stacks that combine Vue with Laravel via Inertia.js.

Vue 3 & Composition APINuxt 3PiniaInertia.js

Vue as the pragmatic default for Dutch teams.

Vue is surprisingly dominant in the Netherlands. Many agency teams coming from a PHP and jQuery background pick up Vue faster than React: the template syntax looks like HTML with directives, single-file components keep markup, logic and styling visually together, and the learning curve is gentler for a back-end developer than with a JSX-based framework. Vue feels familiar to people who have worked with Blade, Twig or Smarty templates, which explains why you see it so often in education, government and SME portfolios.

A Vue stack is therefore not an exotic choice but a solid standard. The ecosystem is mature, the release cycle predictable, and the tooling around Vite, Nuxt, Pinia and VueUse shares the same mindset: small API surfaces, explicit defaults, as little magic as possible. For product teams who want to keep a fast iteration pace without switching paradigm every two years, that is a comfortable foundation. We build Vue projects as part of our broader range of web development, alongside Astro, React and Laravel projects.

The question that always comes up in our first conversations is not whether Vue is technically suitable (it almost always is) but whether it is the right choice for your team and your product. Sometimes Vue really is the pragmatic default. Sometimes React is a better fit, when Next.js or the broader React ecosystem is decisive. Sometimes Svelte is more interesting, and very occasionally Angular remains the right answer when you have an existing Angular codebase. We have that honest conversation before a single line of code is written.

Three typical Vue projects.

The Vue enquiries we receive usually fall into one of three patterns. Which one fits depends on whether you want an interactive web application, a marketing or content site that runs as a static export, or a hybrid product with server-side rendering and routing. We advise on the right approach during the scoping phase.

Compact project · fixed sprint budget

Vue web application or customer portal

A logged-in Vue app for a defined audience: a customer portal, a dashboard, a planning tool or an internal workspace. Vue 3 with the Composition API on the front end, a REST or GraphQL API underneath, Pinia for state, Vue Router 4 for navigation and a component library such as PrimeVue, Naive UI or Vuetify for the building blocks. Well suited to B2B portals, vendor dashboards and internal tooling.

Vue 3 + VitePiniaVue RouterPrimeVue / Naive UI
Mid-sized project · fixed sprint budget

Nuxt website with SSR or SSG

A marketing site, product catalogue or content platform built on Nuxt 3. Server-side rendering for SEO and first-paint performance, static generation for pages that rarely change, and hybrid rendering for combinations: static for the homepage, server-rendered for search results, client-side for the logged-in dashboard. Edge deployment via Cloudflare Pages, Vercel or Netlify keeps TTFB low.

Nuxt 3Hybrid renderingNitro server routesEdge deployment
Larger project · fixed sprint budget

Laravel + Vue via Inertia.js

A combination that is in high demand in the Netherlands: a Laravel backend for data, auth and business rules, with Vue as the front end and no need to write a separate API layer. Inertia.js passes props straight from the controller to Vue pages, keeps the SPA experience and keeps the mental model close to a classic server-rendered app. Ideal for SaaS products, e-commerce and business applications where Laravel is already the choice.

LaravelInertia.jsVue 3Eloquent + Pinia

The technology choices we make.

A Vue project is more than just the framework. Each of the choices below affects build speed, maintainability and how well your team can still maintain the codebase in a few years' time. A quick tour of what we typically use and why.

Framework

Vue 3 with the Composition API

Vue 3 is the current major version and the standard for new projects. We work consistently with the Composition API and <script setup>syntax: less boilerplate, better TypeScript inference and composables you can reuse across projects. We support the Options API in legacy projects where migration is not a priority, but we never start new codebases that way.

Meta-framework

Nuxt 3 for SSR and SSG

Nuxt 3 is to Vue what Next.js is to React: file-based routing, built-in server routes via Nitro, auto-imports, hybrid rendering and data-fetching utilities that standardise what would otherwise be built from scratch. For sites that need SEO or a server-rendered first paint, Nuxt is the default. For pure logged-in SPAs, we use Vue 3 with Vite and no Nuxt to keep the architecture simpler.

State management

Pinia as the successor to Vuex

Since 2022, Pinia has been the state library officially recommended by the Vue team and the de facto standard. The API is type-safe, the devtools integration is excellent and the stores are composables under the hood, which fits the Composition API seamlessly. We no longer use Vuex for new projects; existing Vuex codebases we migrate to Pinia incrementally where it makes sense.

UI components

Vuetify, PrimeVue, Naive UI or Vueform

Vuetify is the familiar choice with Material Design, suitable when brand consistency is not a hard requirement. PrimeVue offers a broad range and is strong for enterprise dashboards. Naive UI is light and flexible for projects that want to feed their own design system. We reserve Vueform for form-heavy applications such as quote flows, long registration forms and configurators. For fully custom work we start with Headless UI Vue plus Tailwind.

Forms and validation

VeeValidate or Formkit

Forms are where many web applications get stuck: validation that drifts out of sync with the backend, poor error states, inaccessible labels. We work with VeeValidate combined with Zod or Yup schemas that we share between client and server. In Vueform or Formkit projects we use their own schema layer, with the same rule: one source of truth, used by both client-side and server-side validation.

Testing

Vitest plus Playwright

Vitest is the Vite-native test runner: fast, and using the same configuration as your build. For unit tests of composables and utilities, it is the right tool. For components, we use Vue Test Utils on top of Vitest. End-to-end tests run on Playwright, sometimes supplemented with Cypress when a team already has experience with it. CI runs both suites on every pull request, so regressions are caught there, not at the demo.

Utilities

VueUse as the Swiss army knife

VueUse is a collection of hundreds of composables for browser APIs, sensors, the clipboard, geolocation and network detection. Almost every project we do leans on it. The composables are tree-shakeable, so only what you use ends up in the bundle. For utilities VueUse doesn't have, we write our own composables following the same conventions.

Styling and hosting

Tailwind plus Vercel, Netlify or Cloudflare Pages

Tailwind is our default for styling on most projects: fast iteration and good co-location with the template. For Nuxt 3, Vercel and Netlify are the most obvious deployment targets, with first-class support and preview URLs per pull request. We choose Cloudflare Pages when edge distribution or a low TTFB in Europe matters. Self-hosting is also an option: Nuxt behind a Node server in Docker, alongside your existing infrastructure.

What you get at the end.

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

  • The Vue application in production and stagingTwo environments, running in your cloud (GCP, AWS, Azure, Cloudflare) or with us. A CI/CD pipeline ready for further development, with preview builds per pull request.
  • TypeScript codebase plus design systemThe full source with TypeScript from start to finish, documented single-file components, a Histoire or Storybook catalogue, and design tokens that capture your brand in code.
  • Server or API layerNuxt server routes, a separate REST or GraphQL API, or a Laravel backend when we opt for Inertia.js. An OpenAPI or GraphQL schema, with a typed client so the front end and back end never drift out of sync.
  • Test suite and performance budgetVitest unit tests, Playwright end-to-end tests, accessibility checks against WCAG 2.2 AA, and clear Core Web Vitals targets that we verify for every release using Lighthouse and WebPageTest.
  • Documentation and runbookAn architecture overview, deployment instructions, an incident runbook and a short developer onboarding guide showing how someone can be productive in the codebase from day one.
  • Maintenance contract (optional)Monitoring, dependency updates, security patches and further development. A fixed monthly price, different response-time levels, and the guarantee that the codebase doesn't stand still.

When Vue is the right choice.

Four patterns where a Vue stack really adds value. If you recognise your situation here, we'd be happy to talk further. And if Vue isn't a good fit, we'll say so in the first conversation.

Dutch team context

From PHP and jQuery to an SPA

Your own team comes from a PHP or Laravel background and has worked with server-rendered templates for years. The step to an SPA feels big. Vue's template syntax, single-file components and gentler learning curve make that transition smoother. Many Dutch agency teams choose Vue over React for this reason.

Product development

Keeping a fast iteration pace

You have a product that evolves continuously: new features every sprint, A/B tests, copy changes. The Composition API and Vite's hot module replacement keep the feedback loop short, and Vue's reactivity avoids a lot of the boilerplate you would write in other frameworks. You notice the difference in iteration speed straight away.

Customer portals and dashboards

Logged-in tooling with state

You're building an environment where users spend longer sessions: a customer portal, a dashboard, a planning tool. Vue 3 with Pinia handles complex client state elegantly, and the enterprise component libraries (PrimeVue, Vuetify) provide all the tables, forms and widgets you typically need.

Laravel + Vue via Inertia

No separate API layer

Your backend is Laravel and you want a rich front end without writing a separate REST or GraphQL layer. Inertia.js gives you an SPA experience where the Laravel controller sends props directly to Vue pages. You keep the mental simplicity of a classic server-rendered app, but get the UX of an SPA. Popular in the Netherlands, and rightly so.

And when Vue isn't the best choice.

Vue isn't a universal solution. In these situations we more often advise something else. We'd rather give honest advice than automatically push our own preferred framework.

Enterprise context

When the React ecosystem is decisive

For enterprise projects where deep integration with Next.js, the React ecosystem or a React monorepo strategy is central, React is often the more pragmatic choice. It's easier to find capacity on the market, third-party libraries support React first and Vue later, and your team can move to React Native for mobile without starting over.

Legacy stack

Existing Angular codebase

Do you already have a production Angular app that your team is productive in? Migrating to Vue is rarely the right investment. Angular is a mature framework with an active roadmap, and the pain of migrating almost never outweighs the gain. We're happy to help with modernisation within Angular itself (a new Angular version, signals, standalone components) rather than a framework switch.

Bleeding edge

React Server Components patterns

Do you explicitly want to work with React Server Components, Server Actions or a Next.js App Router pattern that sits on the bleeding edge? That ecosystem lives in React. Vue has its own strong server rendering through Nuxt and Nitro, but if you specifically need the RSC approach, choose React. We're honest about that.

Pure content site

A marketing site without much interaction

For a purely content-driven site (a blog, brochure site or knowledge base without a logged-in flow), Astro or a classic server-rendered stack is often a better fit than Nuxt. Vue tooling for logged-in users on top of an Astro public site is a workable combination that we deliver regularly, and it's usually cheaper than building everything in Nuxt.

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 →

Vue versus React and Svelte.

The three frameworks you would realistically consider for a new web project are Vue, React and Svelte. Each has strengths and honest drawbacks. None of the three is universally better; the context determines which one fits. Here's the short version.

Strong in · readability and Dutch adoption

Vue 3

Strong in: readable template syntax, a lower learning curve for back-end developers, a smaller default bundle than React, seamless use with Laravel via Inertia, and a strong presence in Dutch education and agencies. Less strong in: its enterprise market share in the Netherlands is smaller than React's, and the English-language ecosystem is thinner.

Composition APINuxt 3Inertia.jsPinia
Strong in · ecosystem and talent pool

React

Strong in: the largest ecosystem of the three, the most third-party libraries, the largest talent pool and therefore the lowest capacity risk, plus a direct path to React Native for mobile through shared components. Less strong in: JSX and a more complex mental model for people without a front-end background, and a larger baseline bundle than Vue or Svelte.

Next.jsReact NativeLargest ecosystemTanStack Query
Strong in · compile-time efficiency

Svelte

Strong in: its compile-time approach means a smaller runtime and cleaner syntax than Vue and React, and SvelteKit as a complete meta-framework feels very productive. Less strong in: the ecosystem is noticeably thinner, third-party component libraries are more limited, and the talent pool is smaller in the Netherlands. A fine choice for performance-critical projects or for teams that deliberately want to keep things small.

SvelteKitCompile-timeSmall ecosystemPerformance focus

How a Vue project works with us.

1

Introduction and scoping

A no-obligation conversation in which we learn which flows the Vue application needs to support, how it fits into your existing landscape, and whether an SPA, an SSR site or a hybrid approach is the best answer. We often compare Vue with React here as well, and if React is the honest choice, we'll say so.

2

Tech choices and UX workshop

Together we decide on the framework (Vue 3 with or without Nuxt), the state approach (Pinia or not), the UI component library (PrimeVue, Naive UI, Vueform or headless), 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. For Laravel stacks, this is where we choose between Inertia.js and a separate API layer.

3

Building in sprints

A working build you can test every two weeks. We build horizontally: first a working end-to-end flow with one role, then more depth, then additional roles or modules. Performance budget, accessibility checks and TypeScript strictness are in place from sprint one. Pull requests are reviewed, preview builds roll out automatically, and you can steer at any time.

4

Hardening, rollout and handover

In the final sprints, we run an accessibility audit (WCAG 2.2 AA), a Lighthouse report and a penetration test. This is followed by a phased rollout to your users and a formal handover with documentation. We can handle maintenance for you, or hand over cleanly to your own team with a runbook, a handover session and optional backup support for the first few months.

Fabian van Dijk Business developer · Appfront

First point of contact for Vue projects at Appfront. Reach him at fabian.vandijk@appfront.nl for a no-obligation introductory chat about when Vue fits your stack — and when React, Svelte or a Laravel + Inertia combination is the honest answer.

Frequently asked questions about Vue.

The questions clients ask before we start a Vue project.

Vue or React: which should we choose?
Choose Vue when your team comes from a PHP or Laravel background, you want to use Inertia.js, or you find the template syntax more readable than JSX. Choose React when you want Next.js, need a large React ecosystem, or may later want to move to React Native for mobile with shared components. Both work for 90 percent of projects; the context decides which one fits.
Is Vue future-proof? Is it still maintained?
Yes. Vue 3 is the current major version, with predictable release cycles and LTS versions. Pinia has officially succeeded Vuex, Vue Router is at version 4 and Nuxt 3 is a thorough rewrite. The Vue team works closely and consistently with the maintainers of Vite, Vitest and Nuxt, so the whole ecosystem evolves in the same spirit. In the Netherlands, Vue is dominant among agencies, educational institutions and SMEs, which keeps the talent pool stable.
What exactly is Inertia.js and when do you choose it?
Inertia.js connects Laravel (or another server-rendered backend) to Vue without you having to write a separate REST or GraphQL API. The Laravel controller sends props directly to Vue pages, Inertia handles navigation client-side like an SPA, and you keep the mental model of a classic server-rendered application. We choose Inertia.js when a single team maintains both front end and back end, and a separate API layer for a single consumer would be over-engineered.
What about SEO for a Vue site?
SEO with Vue is not a problem as long as you choose the right setup. For public pages that need to rank highly, we use Nuxt 3 with server-side rendering or static generation, which delivers complete HTML that Google can index directly. We vary by page type: prerendering for pages that rarely change, SSR for pages that change regularly, and client-side rendering for the logged-in dashboard. We advise against a pure client-side SPA for the public site, as first paint and consistency are better with SSR.
Can you also migrate an existing Vue 2 application?
Yes. Vue 2 reached end-of-life at the end of 2023 and no longer receives security updates, so migrating is inevitable at some point. We do it incrementally: first to Vue 2.7 (which backports the Composition API), then to Vue 3 using the official Migration Build, which lets both versions run in parallel. Vuex to Pinia and Options API to Composition API happen in the pages we're touching anyway. No big-bang rewrite.
Which UI component library do you choose?
It depends on the project. PrimeVue for enterprise dashboards with lots of tables and complex forms. Naive UI or Headless UI Vue plus Tailwind for projects where your brand look needs to be pixel-perfect. Vuetify when Material Design is your target aesthetic. Vueform for form-heavy applications such as quote flows. We almost always combine the chosen library with a custom design-system layer, so components remain replaceable without affecting the rest.
How do you handle state management?
Pinia is the standard. For server state we use TanStack Query (Vue version) or Nuxt 3's built-in data fetching, both of which handle caching, refetching and optimistic updates well. We no longer use Vuex for new projects. The principle: as little global state as possible, and what there is belongs in Pinia, not scattered across composables.
Do you work alongside our own developers?
Yes, we do this often. Some clients want us to build the Vue application entirely and then take over maintenance; others want co-development from day one so that their own team can take over the codebase later. We work well in both setups, as long as we agree clear terms up front on code ownership, review protocols and handover. For stacks where we combine Vue with a Laravel backend, we also look at capacity through hiring a full-stack developer, so that one person can pick up both Vue and Laravel.
How do we handle auth in a Vue application?
For customer portals we often choose a hosted IdP such as Auth0 for social logins, SAML and SSO. For privacy-sensitive sectors or on-premise requirements we use Keycloak. In Laravel + Inertia stacks we use Laravel Sanctum for session-based auth and Laravel Passport for token-based auth, with a composable on the Vue side that tracks auth state via Pinia. We only build a custom JWT stack when there is a strong reason to, because auth mistakes are expensive.
What about accessibility and GDPR?
Accessibility is built in from day one: semantic HTML, ARIA where needed, focus management for client-side routing and contrast checks against WCAG 2.2 AA. For B2B applications subject to public tenders or EN 301 549, we also deliver an accessibility report. GDPR compliance is standard: data stays in the EU (Cloudflare EU, Vercel EU regions or your own EU cloud), privacy-by-design architecture, and a DPIA where relevant.
What determines the cost and the lead time?
The number and complexity of the screens, the number of roles and permissions, the depth of the integrations, and whether we also need to build a server layer or API. A well-defined Vue portal with a single role is a different conversation from a Nuxt platform with multiple roles, SSR and three integrations. We work with fixed sprint budgets so you stay in control of spending each sprint, and we commit to a sprint cadence and clear milestones rather than a fixed figure that would do violence to the scope. In the first conversation we outline the scope together and give you an honest indication.

Talk to us about your Vue project.

A half-hour introductory call, no obligation. We listen to what you want to build, look at how it fits with your existing stack and team, and give honest advice (Vue, React, Svelte or a Laravel + Inertia combination) rather than automatically selling our own preferred framework.

If your existing site is slow in PageSpeed Insights, read about improving Core Web Vitals.

Edit content