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.