Custom websites and web applications built on Vue 3 with the Composition API, Nuxt for SSR and SSG, and Pinia for state. Ideal for product teams who want to iterate quickly, for customer portals, dashboards and e-commerce, and for Dutch stacks that pair Vue with Laravel via Inertia.js.
Vue is surprisingly dominant in the Netherlands. Many agency teams coming from a PHP and jQuery tradition 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 is predictable, and the tooling around Vite, Nuxt, Pinia and VueUse shares the same philosophy: small API surfaces, explicit defaults, and as little magic as possible. For product teams who want to sustain iteration speed without switching paradigms every two years, that is a pleasant foundation. We build Vue projects as part of our broader web development offering, alongside Astro, React and Laravel projects.
The question that always comes up in our first conversations is not whether Vue is technically suitable, which it almost always is, but whether it is the right choice for your team and your product. Sometimes Vue is indeed the pragmatic default. Sometimes React fits better, where Next.js or the broader React ecosystem is decisive. Sometimes Svelte is more interesting, and very occasionally Angular remains the right answer for an existing Angular base. We have that honest conversation before a single line of code is written.
The Vue requests 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 shape during the scoping phase.
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 as the front end, a REST or GraphQL API behind it, Pinia for state, Vue Router 4 for navigation and a component library such as PrimeVue, Naive UI or Vuetify for the building blocks. Suited to B2B portals, vendor dashboards and internal tooling.
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.
The combination that is in great demand in the Netherlands: a Laravel back end for data, authentication and business rules, with Vue as the front end, without you needing to write a separate API layer. Inertia.js sends props directly from the controller to Vue pages, preserving the SPA experience and keeping 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.
A Vue project is more than just the framework. Each of the choices below affects build speed, maintainability and how well your team can keep the codebase going in a few years' time. A brief tour of what we typically use and why.
Vue 3 is the current major version and the standard for new projects. We consistently work 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.
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 custom-built. For sites that need SEO or a server-rendered first paint, Nuxt is the default. For purely authenticated SPAs we use Vue 3 with Vite without Nuxt, to keep the architecture simpler.
Since 2022, Pinia has been the officially recommended state library of the Vue team and the de facto standard. Its API is type-safe, its devtools integration is excellent, and its stores are composables under the hood, which fits seamlessly with the Composition API. We no longer use Vuex for new projects; existing Vuex codebases we migrate incrementally to Pinia where that makes sense.
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 are where many web applications get stuck: validation that falls out of sync with the back end, 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, following the same rule: one source of truth, used for both client-side and server-side validation.
Vitest is the Vite-native test runner, fast and sharing 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 where a team already has experience with it. CI runs both suites on every pull request, so we catch regressions there rather than at the demo.
VueUse is a collection of hundreds of composables for browser APIs, sensors, 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 does not provide, we write our own composables following the same conventions.
Tailwind is our default for styling on most projects: it allows for fast iteration and sits well alongside the template. For Nuxt 3, Vercel and Netlify are the most obvious deployment targets, with first-class support and preview URLs for each pull request. We choose Cloudflare Pages when edge distribution or low TTFB in Europe matters. Self-hosting is also an option: Nuxt behind a Node server in Docker, alongside your existing infrastructure.
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.
Four patterns where a Vue stack genuinely adds value. If you recognise your situation in any of these, we're happy to continue the conversation, and if Vue isn't a good fit, we'll tell you that in the first conversation too.
Your own team comes from a PHP or Laravel background and has worked with server-rendered templates for years. The move to an SPA feels like a big step. Vue's template syntax, single-file components and gentler learning curve make that transition smoother. For this reason, many Dutch agency teams choose Vue over React.
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 much of the boilerplate you'd write in other frameworks. You'll notice the difference in how quickly you can iterate.
You're building an environment where users spend long sessions: a customer portal, a dashboard, a planning tool. Vue 3 with Pinia handles complex client-side state elegantly, and enterprise component libraries (PrimeVue, Vuetify) provide the tables, forms and widgets you typically need.
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 passes props directly to Vue pages. You keep the mental simplicity of a classic server-rendered app while getting the UX of an SPA. It's popular in the Netherlands, and rightly so.
Vue is not a universal solution. In these situations we more often recommend something else. We'd rather give you honest advice than automatically push our preferred framework.
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. You'll find it easier to recruit talent, third-party libraries target React first and Vue later, and your team can move to React Native for mobile without starting over.
Do you already have a production Angular app that your team works in productively? Migrating to Vue is rarely the right investment. Angular is a mature framework with an active roadmap, and the migration pain almost never outweighs the gains. We're happy to help you modernise within Angular itself — a newer Angular version, signals, standalone components — rather than switching frameworks.
Do you want to work explicitly with React Server Components, Server Actions or a Next.js App Router pattern at the cutting edge? That ecosystem lives in React. Vue has its own strong server rendering via Nuxt and Nitro, but if you specifically need the RSC approach, choose React. We're honest about that.
For a purely content-driven site — blog, brochure, knowledge base without a logged-in flow — Astro or a classic server-rendered stack is often a better fit than Nuxt. Vue-based tooling on top of a public Astro site is a workable combination we deliver regularly, and it's usually cheaper than building everything in Nuxt.
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →The three frameworks you realistically consider for a new web project are Vue, React and Svelte. Each has genuine strengths and honest drawbacks. None of the three is universally better — the context determines which fits. Here they are at a glance.
Strong in: readability of the template syntax, a gentler learning curve for back-end developers, a smaller bundle than React by default, seamless integration with Laravel via Inertia, and a strong presence in Dutch education and agency circles. Less strong in: its enterprise market share in the Netherlands is smaller than React's, and the English-language ecosystem is thinner.
Strong in: the largest ecosystem of the three, the most third-party libraries, the biggest talent pool and therefore the lowest capacity risk, plus a direct route to React Native for mobile via shared components. Less strong in: JSX and a more complex mental model for people without front-end background, and a larger baseline bundle than Vue or Svelte.
Strong in: the compile-time approach means a smaller runtime, cleaner syntax than Vue and React, and SvelteKit as a complete meta-framework feels very productive. Less strong in: the ecosystem is clearly thinner, third-party component libraries are more limited, and the talent pool in the Netherlands is smaller. A sound choice for performance-critical projects or teams that deliberately want to keep things small.
A no-obligation conversation in which we understand which flows the Vue application must 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 too — and if React is the honest choice, we'll say so.
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 stacks involving Laravel, we make the choice here between Inertia.js and a separate API layer.
A working build you can test every two weeks. We build horizontally: first a working end-to-end flow with one role, then deeper functionality, then additional roles or modules. Performance budgets, accessibility checks and TypeScript strictness are part of the process from sprint one. Pull requests are reviewed, preview builds deploy automatically, and you can steer the project at any point.
In the final sprints, we run an accessibility audit (WCAG 2.2 AA), a Lighthouse report and a penetration test. After that, we roll out in phases to your users and hand over formally with documentation. We can manage the system on your behalf, or hand over cleanly to your own team with a runbook, a handover session and optional support for the first few months.
The questions clients ask before we start a Vue project.
A thirty-minute introductory call, with no obligation. We listen to what you want to build, look at how it fits your existing stack and team, and give you honest advice — Vue, React, Svelte or a Laravel + Inertia combination — rather than automatically selling our own preferred framework.
Appfront uses cookies and similar technologies to keep the website working properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
