Why Vue?
Vue has been my primary frontend framework at KnausDev since the Vue 2 era, and I’ve grown with it through every major shift — Vue 3, the Composition API, Vite as the build tool of choice, and the move from Vuex to Pinia for state management. It hits the right balance for me: approachable enough to drop into an existing page as inline interactivity, structured enough to build a full SPA on, and pragmatic enough to pair cleanly with whatever backend the project demands.
The right level of abstraction
I’d put my level here at proficient rather than expert — a meaningful distinction, but enough to confidently lead frontend on production projects for clients like E-wire and Exlink. Vue lets me focus on solving the actual problem instead of fighting the framework.
How I Use It
Vue is the layer where I take ownership on most of my work at KnausDev. I’ve used it in nearly every configuration the framework supports:
What I build with Vue
- Standalone SPAs: Vite + Vue 3 applications with Vue Router and Pinia, deployed independently from the backend
- PWAs: progressive web apps with offline capability and native-like behavior
- Ionic mobile apps: cross-platform mobile applications built on Vue 3
- Inline interactivity: drop-in Vue components for pages that don’t need a full client-side framework
- Legacy modernization: converting jQuery-heavy codebases into structured inline Vue components as part of system migration projects
My current SaaS, Dadooo.ai, runs fully on Vue 3 as both an SPA and a PWA, while the Exlink platform uses inline Vue components integrated directly into the Laravel backend — two ends of the spectrum, both in production.
What Makes It Great
- Scales cleanly from a single inline component to a full enterprise SPA without architectural rewrites
- Deploys as a standalone Vite app — frontend and Laravel backend stay in separate repos, connected through REST APIs
- Pairs naturally with TypeScript — typed props, composables, and Pinia stores
- Composition API gives the structure needed for complex apps with significantly less boilerplate and friction
Status
Active: primary frontend framework for platform engineering and product development.