Vue.js.
I've shipped Vue on one project: a crypto transaction platform tracking traders, exchange accounts, coins and banks, with a dashboard that resolves what was actually paid in commission to each platform and bank. I've also used Nuxt on a city discovery and rating platform, consuming a REST API. That is the honest extent of it. React is my default frontend and I have far more mileage there, so I would rather state that plainly than talk up a framework I have used once. Vue is genuinely good, the mental model overlaps heavily with React, and on an existing Vue codebase I would work with it rather than propose a rewrite that buys you nothing.
An approachable learning curve
A team without deep JavaScript specialists picks Vue up faster than React. That matters more than my preferences when they are the ones maintaining it after launch.
Dashboards and data-heavy screens
The crypto platform was exactly that: traders, accounts, transactions, and totals that have to reconcile. Vue handled it without complaint.
Nuxt for server-rendered fronts
On the city discovery platform, Nuxt consumed the REST API and rendered the listing pages — much the same role Inertia plays for me elsewhere.
It pairs with Laravel the same way
Inertia treats Vue as a first-class adapter, so the Laravel-owns-routing-and-auth pattern I use with React is available unchanged — though I haven't yet shipped that particular combination.
The most common honest reason, and a good one. I work with what is there instead of proposing a rewrite you do not need and should not pay for.
The framework your maintainers understand beats the one I prefer. A team that can look after the code is worth more than my defaults.
What the crypto platform was: tables, filters and figures that must add up, with the backend owning every calculation. Vue is comfortable here.
For a greenfield project with no Vue history and no Vue team, I would propose React or Livewire instead — not because Vue is worse, but because I have shipped one Vue project and many React ones, and you deserve the framework I am deepest in. If Vue is central to your product and you want real depth, hire a Vue specialist. That is a fair answer and I will give it.
Vue sits where React usually sits in my stack: a presentation layer over a Laravel core that owns the domain, the data and the auth. The boundary does not move just because the framework changed — the crypto platform's ledger and commission logic lived in Laravel, and the Vue front end read it.
One production project, plus Nuxt on a second. I'd rather tell you that than imply a depth I don't have. If Vue is central to your project and you need a specialist, hire one — I'll say so in the first call, not the third month.
Yes. Vue and React overlap heavily in mental model, and the hard part of maintaining an app is rarely the frontend framework — it is the backend, the data and the tests, which is where I am strongest.
React, unless you have a Vue team or a Vue codebase — in which case Vue, and I would not fight it. Both are good frameworks. The real tiebreaker is who maintains it after I am gone.
In my work
One shipped Vue project: a crypto transaction platform where commission cost to each exchange and bank is visible rather than inferred. Plus Nuxt on a city discovery platform.