Skip to content

Vue

I reach for Vue when a page needs to be genuinely interactive but doesn’t need to become a heavyweight application — and most pages that “need React” are actually in exactly that spot. The problem people bring me here is usually one of proportion: they want a slick interactive feature, and the default advice has them building a full single-page app and throwing away their server-rendered HTML to get it. Vue, used well, gives you the interactivity without paying that whole bill. Knowing where that line sits is the value.

The problems I solve here

The first is the page that should stay server-rendered but needs islands of real interactivity — a configurator, a live filter, a multi-step form, a calculator. The instinct is to rebuild the whole thing as an SPA. The better answer is to keep the page rendered on the server, fast and good for search engines, and mount Vue components onto just the parts that need to come alive. I’m brought in to do that cleanly, or to undo the over-built version someone already committed to.

The second is the front end that got heavy for no good reason. A team chose a maximal framework and tooling stack for a UI whose actual interactivity is modest, and now they’re carrying weight and complexity they never needed. The work is to right-size it — sometimes that’s a move to leaner Vue, sometimes just cutting the ceremony out of what’s there.

The third is the interactive feature that has to be added to an existing, mostly-static site without rebuilding it. Vue drops into that situation better than almost anything, and the job is to add the capability without disturbing what already works.

How I think about Vue

Vue’s strength is that it scales down gracefully. You can use it for one component on one otherwise-static page, or for a full application, and it doesn’t force the maximal version on you to get the small one. That progressive quality is exactly what most projects actually need and rarely get, because the prevailing fashion is to start at the heaviest option and never ask whether it was warranted.

So my main call with Vue is almost always the same: keep the rendering on the server and let Vue handle only the interactive parts. Server-rendered HTML is faster to first paint, better for SEO, simpler to reason about, and cheaper to maintain. Layering Vue on top of it — the hybrid approach — gives you the interactivity exactly where it’s needed and nowhere it isn’t. I’ll choose that over a full client-side rebuild almost every time, and the cases where I won’t are the genuinely app-like interfaces where I’d be weighing Vue against React on the merits, not defaulting to either.

The mistake I see and fix is treating the front-end framework as the whole architecture — pulling data fetching, business logic, and state into the browser where it doesn’t belong, leaving a thin backend and a fat, fragile client. The framework is a presentation tool. The logic and the data should stay on systems you own. Vue done well is a light, sharp layer over a solid owned backend, not a place your business ends up living.

How I’d actually do it

Take a business with a fast, server-rendered site that now needs an interactive quoting tool. The default path rebuilds the site as an SPA to accommodate one feature. What I’d do instead is leave the site exactly as it is and mount a single Vue component where the tool goes — it talks to an API for the numbers, handles the interaction in the browser, and the rest of the page stays the simple, fast, indexable thing it already was. Smaller change, less to maintain, nothing thrown away, and the data and logic stay in the owned backend where they belong.

I keep the Vue itself deliberately plain — the modern composition style, minimal extra state machinery, no library reached for until the problem actually demands it. Most front-end complexity is self-inflicted. The lean version is almost always the right one, and it’s the one the next person can still read.

Where this connects

This is one of the specialisms I’m hired for. Vue is the front-end partner to a Laravel backend in most of what I build — the interactive layer over the owned engine — and it’s the lighter counterpart to React when an interface genuinely is an application. When the question is whether you need a full client-side app at all, that’s the single-page apps decision. The engagement this most often powers is an MVP development, where keeping the front end lean is part of shipping fast.

When you need a team instead

A large Vue application under continuous feature development is team work, not one-person work — that’s my agency, Digital Royalty, with the crew to build and run it at scale. My lane is the senior call on how much front end you actually need and the lean build of it. I’ll tell you straight which one fits.

Who this isn’t for

If you’ve already decided you want a full single-page app and just want hands to build it, I’m probably not your fit — I’ll question whether you need one first. I’m worth hiring when you want the right amount of front end, not the maximal amount.

Talk to me

If you need a page to do more without becoming a heavyweight app, tell me about your problem and I’ll tell you the lightest way to get there.