Vue.js development

Build progressive, high-performanceweb applications with Vue JS

Vue can start as a small interactive part of an existing page and grow into a full single-page application. We build in Vue 3 and move Vue 2 applications forward. Vue 2 has been out of support since the end of 2023, so that second job is often the urgent one.

Discuss your Vue applicationSee Nuxt development

What Vue work covers

Vue's flexibility means projects can look quite different from each other.

  • Single-page applications

    Dashboards and logged-in tools in Vue 3 with the Composition API, Vue Router and Pinia, talking to your API.

  • Interactive parts of existing pages

    A pricing calculator or a filtered list added to a server-rendered site, without rewriting the rest. This is where Vue's incremental design is most useful.

  • Migrating from Vue 2

    Moving components, then updating or replacing the libraries tied to Vue 2. UI kits and plugins with no Vue 3 release can take more time than the components themselves.

  • Performance and maintainability work

    Splitting oversized components, adding lazy-loaded routes and introducing TypeScript to a codebase that has grown without it.

Vue versions, as of October 2026

Vue's release page and npm are the sources for these.

  • Current: Vue 3.5

    npm lists 3.5.44 as the latest release. New work starts here, using the script setup syntax with single-file components.

  • Vue 2 is end of life

    Vue 2 reached end of life on 31 December 2023, so the free project releases no more fixes for it. A Vue 2 app in production is carrying an unpatched dependency.

  • No fixed schedule

    Vue has no fixed release cycle. Minor versions typically arrive 3 to 6 months apart after a beta, and majors are announced ahead of time. You plan around that, not around dates.

Vue, React or something else

Vue is rarely the wrong technical choice, so the deciding factors are practical.

  • Choose Vue when

    You want a framework with official router and state libraries from the same project, or you need to add interactivity to server-rendered pages without a big build.

  • Choose React when

    Your team already knows it, you want React Native later, or you depend on libraries that are only available for React.

  • Use Nuxt on top when

    Pages need to rank in search or load quickly for first-time visitors. Plain Vue renders in the browser, so that case needs server rendering.

  • TypeScript caveat

    Microsoft advises projects relying on Vue's editor tooling to stay on TypeScript 6.0 for now, because TypeScript 7.0 has no compiler API for that tooling to use.

How a Vue 2 migration runs

New Vue 3 builds follow similar steps, without the first two.

  1. List the dependencies

    Each Vue 2 library is marked as having a Vue 3 version, a replacement, or nothing. This list sets the size of the job.

  2. Choose a route

    Vue's migration build offers Vue 2 compatible APIs, which suits some apps. For others, moving screens gradually into a new Vue 3 app is cleaner.

  3. Move and test in slices

    Shared components move first, followed by the routes, and tests are added around the behaviour before each slice is changed.

  4. Remove the compatibility layer

    The job isn't finished until the compatibility build is gone and the app runs on plain Vue 3. Otherwise you have only moved the problem.

How to engage us on Vue

The dependency list normally decides which model makes sense.

With the dependency list done, a Vue 2 migration can be priced in stages or run as time and materials. We can also add a Vue developer to your team. Our hourly rate starts from $20/h in USD, invoiced in USD, GBP, EUR or INR.

We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment. We can review pull requests with your developers during the shared hours. For the API behind the screens, see Laravel and Node.js.

Why no Vue applications are named here

Most of our work is delivered under NDA, so many projects cannot be named.

Rather than name-drop, this page sets out how we approach Vue work. You will learn more by sending us your package.json, which shows us what a migration would involve.

Questions about Vue

Most of them come from people still running Vue 2.

Is it safe to stay on Vue 2?
It keeps working, but it no longer gets fixes from the Vue project, and its ecosystem is moving on. For a public or sensitive app, plan a move or arrange paid extended support from a third party until you can.
Can we migrate gradually?
Usually. The migration build runs much Vue 2 code on Vue 3 while you convert it, or screens can move across one route at a time. Which suits you depends on how closely the app is tied to old libraries.
Do we have to rewrite in the Composition API?
No. The Options API still works in Vue 3, so existing components can move without being rewritten. Use the Composition API for new code, and where the logic needs sharing.
Would Vue suit a public marketing site?
Only with server rendering, which normally means Nuxt. A plain client-rendered Vue app is a poor base for pages that have to perform in search.

Send us your package.json

It shows the Vue version and the libraries behind your app. From that we can tell you the main risks and how we would approach them.

Start a Vue conversationSee Nuxt development

We reply within one business day (IST).