What we build with it
Vue is our default for browser UI. We use it for the interfaces that sit behind a product rather than in front of it — merchant dashboards, configuration panels, internal admin tools — and for customer-facing web apps.
The reason is maintainability rather than novelty. The Composition API keeps logic extractable and testable, the single-file component keeps a screen's markup, behaviour and styles in one readable place, and the framework changes slowly enough that a project written two years ago still builds and still reads like current Vue.
Where we have shipped it
The merchant and admin interfaces of our white-label cashback platform are Vue — the surfaces where shop owners configure cashback rules and where new branded apps are launched.
When we recommend it
Vue suits teams that will own the code after we hand it over. It is approachable enough that a backend-leaning developer can make a safe change to a screen, which is often the real constraint on a small team.
We would suggest something else if your team is already deep in React and hiring against it — framework familiarity beats framework preference. For anything server-rendered or SEO-sensitive we reach for Nuxt rather than plain Vue.
