---
title: "Vue | Skills We Assign For | Azendo"
description: "Vue on long-lived frontends — what the official ecosystem avoids, the Vue 2 to 3 question, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/vue/"
---

[Skills](https://azendo.co/skills/) Frontend frameworks and tooling 

# Vue.

Vue is a frontend framework built around single-file components and a reactivity system that tracks dependencies automatically. It occupies a middle ground: more structure than a library, less ceremony than a full framework, with an official router and state layer rather than a choice between competing ones.

## Where Vue fits on a long engagement.

Vue's practical advantage is that the ecosystem decisions are already made. Router, state management and build tooling are official, so a Vue codebase from three years ago generally uses the same pieces as one written today. That removes an entire category of archaeology that other frontend stacks impose on whoever inherits them.

The live question on most Vue estates is Vue 2 versus Vue 3\. Vue 2 reached end of life at the end of 2023, and applications still on it are accumulating a security and dependency problem rather than a stylistic one. The migration is usually tractable, but it is real work and it does not get cheaper by waiting.

## What an assigned team does with Vue.

Frontend assignments produce the most visible output on a roadmap, which makes them the easiest to fill with feature work and the easiest to let rot underneath. A standing assignment is where component consolidation and accessibility fixes actually happen, because there is a next quarter to hold them in.

Vue work is rarely useful in isolation from the design that specifies it. Where the components and the design system are the same artefact seen from two sides, that capacity is scoped together under [outsource ux design](https://azendo.co/services/ux-ui-design/) on one agreement.

## What we use Vue for.

* Applications with long-lived internal screens Admin and operations interfaces where consistency matters more than novelty, and the official ecosystem keeps dependencies boring.
* Vue 2 estates past end of life A staged migration to Vue 3 that keeps the application shipping rather than a rewrite nobody can justify.
* Incremental adoption in an older page Vue mounted into part of an existing server-rendered application, so modernisation does not require a big-bang release.

## How Vue capacity is assigned.

Vue specialists are assigned under [outsource software development services](https://azendo.co/services/software-development/), most often alongside a designer on the same agreement rather than as an isolated frontend booking.

## Roles we assign Vue for

* [Frontend Developer Software development](https://azendo.co/services/software-development/frontend-developer/)

## Service lines it sits in

* [Software development](https://azendo.co/services/software-development/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in frontend frameworks and tooling

* [Webpack — skill we assign for](https://azendo.co/skills/webpack/)
* [Tailwind CSS — skill we assign for](https://azendo.co/skills/tailwind-css/)
* [SCSS — skill we assign for](https://azendo.co/skills/scss/)
* [Redux — skill we assign for](https://azendo.co/skills/redux/)
* [Zustand — skill we assign for](https://azendo.co/skills/zustand/)
* [Laravel — skill we assign for](https://azendo.co/skills/laravel/)
* [Angular — skill we assign for](https://azendo.co/skills/angular/)
* [Svelte — skill we assign for](https://azendo.co/skills/svelte/)

## Tell us what your roadmap needs Vue for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)