Vue 3v3

How I came to Vue 3

React and Next.js are my default front-end stack. Vue is the tool I reach for when a team or codebase is already on it — and when I do, I work in it at full speed.

That confidence isn't theory. On ChatFood — the regional order-and-pay platform later acquired by Deliverect — I was hired as a backend developer. Part-way in, the team needed hands on the Vue 3 front-end, and I moved across with zero Vue experience. First merged pull request inside a week. By the end of the first month I was one of the stronger contributors on the front-end, learning the full Vue 3 concept set as I shipped real features.

So when a client's product is built on Vue, switching it to React is rarely the right call. I pick up the existing codebase and keep delivering.

What Vue 3 does well

Vue 3 is a pragmatic front-end framework. It gives you a reactivity model and a component system that are quick to read and quick to be productive in — which is exactly why I could go from zero to shipping in a week.

Composition API and reactivity

The Composition API lets you group logic by concern instead of by lifecycle hook. Reactive state, derived values, and side effects for one feature live together, so a complex screen stays legible as it grows. Vue's reactivity tracks dependencies for you, which removes a whole class of manual wiring — useful on stateful UIs like ordering flows, where carts, totals, and availability all move together.

Single-file components

A Vue single-file component co-locates template, logic, and scoped styles in one file. For a fast-moving product team that's a real advantage: the markup, the behaviour, and the CSS for a piece of UI sit in one place, so changes are local and reviews are easier.

A gentle ramp that holds up

Vue is approachable without being shallow. The mental model is small enough to onboard a backend developer in days, and complete enough to build a production ordering flow on. I lived both ends of that: onboarding fast, then contributing to the shared design system the rest of the team built on.

Vue vs React — my honest take

I won't oversell Vue as my primary stack, because it isn't. React and Next.js are where I do most of my front-end work, and for a greenfield project that's usually what I recommend — the ecosystem, the hiring pool, and my own depth all point there.

When would I actually pick Vue?

• The codebase is already Vue. Rewriting a working front-end to React is a cost with no product upside.
• The team is already Vue. Hiring and onboarding are easier when you build on what people know.
• The product is a form- and state-heavy UI where Vue's reactivity ergonomics genuinely shave time.

The point of saying this plainly is that you get an engineer who'll tell you when a technology is and isn't the right fit — not one selling you a rewrite.

Where I've shipped it

On ChatFood, I built core surfaces of the customer ordering flow in Vue 3:

• The order catalog page — the menu browse-and-select experience.
• The cart — line items, modifiers, and totals kept in sync as the order changes.
• Apple Pay checkout — the payment step that closes the order. (More on the payments side under Payments.)

I also contributed to the design system the front-end team shared, so the components I shipped matched the rest of the product. The backend behind that flow was Laravel — so I was moving across the full stack, not just the view layer.

If your product runs on Vue and you need someone who can step into the codebase and ship — including the checkout and payment paths — that's work I've done. It usually lands under web app development.