Vue.js
Vue.js development when the interface should stay approachable
Vue is a good choice when the interface is a product in its own right and the team wants a framework that is readable without a large amount of ceremony. We also use it to replace parts of an older front end without stopping the business for a rewrite.
- Product interfaces
- Incremental replacement
- Content-plus-app sites
- Accessible forms
What we build
Customer-facing applications, admin tools of moderate size, and islands of new UI inside a legacy page when a full replacement is not justified yet. Nuxt is considered when the public site and the app share a Vue team and rendering on the server matters.
When we steer away from Vue
A very large form-and-workflow programme with many developers often benefits from Angular’s stricter structure, or from React if that is already the company standard. Adding Vue as a third framework in the same product is a cost we try not to create.
Vue when the team will enjoy keeping it
Vue fits
- A focused web app
- Incremental adoption beside existing pages
- A small team that likes the framework
Skip Vue when
- The company standard is already Angular or React
- The job is a native app
- Nobody will maintain the choice
What changes a Vue build
The standard
A second front-end framework is a cost. We need a reason beyond taste.
The pages
A portal and a public site can be different. They should not share a compromise.
The handover
The people who will add a screen have to be in the choice.
Before a Vue app
- 01
The standard
Whether Angular or React is already the company default.
- 02
The reason
A real reason beyond taste.
- 03
The pages
Portal or public site. They need not be the same app.
- 04
The keepers
Who will add a screen next quarter.
Marks Vue is the focused interface
- 01
A focused surface
It is here for a contained product or a part of a larger site.
- 02
It can sit beside
An existing page can stay while this interface is added.
- 03
The store is not the database
The source of truth remains the server record.
- 04
A change can ship
The team who will own it can release a small fix.
What we build
Product interfaces
Clear component boundaries and a data flow the next developer can follow.
Incremental replacement
A new flow beside the old one, sharing the API, until the old flow can go.
Content-plus-app sites
Public pages and a logged-in area when one team owns both.
Accessible forms
Validation and errors that work on a phone and with a keyboard.
Questions we hear
Do you use Vue 3?
Yes for new work. Vue 2 is maintenance and a migration plan.
Can our PHP or Laravel team keep it?
If they are willing to own the front end as a product, yes. We will not leave a Vue build nobody can release.
How does Vue compare with React here?
Both can build the same portal. The better one is the one your team will still understand in two years. We do not treat the choice as a moral question.