**Update:** apparently the title of this post was misleading and started a fight on Twitter. Unfortunately, I can't edit the title, but it should have been something like "Laravel Snippet #24: Taylor talks about SPAs vs Livewire/Inertia" to be less provocative. Sorry if this misguided or insulted anyone.
\- - - - - - - -
Last week Taylor released a new podcast episode of Laravel Snippet, explaining Fortify, Jetstream, Breeze and why they were created. I totally recommend listening to [a full 20-minute episode](https://blog.laravel.com/laravel-snippet-24-fortify-jetstream-breeze), but what struck me was his opinion on the architecture of Vue SPA and Laravel API, which grew pretty popular over the last years. So I will just quote exactly, word for word, what Taylor said, and let's discuss in the comments.
>I had just built Laravel Vapor using a Vue SPA as a front-end architecture, and I just don't enjoy using Vue Router, I don't enjoy writing applications in that style, I think using Livewire or Inertia is a much more productive, much faster development experience.
>Inertia, in my opinion, is a much more productive way to use Laravel and Vue together in one monolithic application, compared to using Vue CLI or React CLI that have a separate SPA.
>I still see people wanting to build these separate SPAs that consume Laravel API, to this day. I really don't think it's a good idea, and I think you should avoid it, if at all possible, because it introduces a lot of complexity, not only in your local development but also in your production deployment strategy. Now you have to deploy two repositories at the same time, and you have to think about bundles, breaking changes of your Laravel API. And, honestly, it's just a headache that you shouldn't volunteer yourself for. If you HAVE to do this for some serious architecture thing at your organization, then fine, but you shouldn't take this unwillingly, this should be like a last-ditch thing that you have to accept.
>Otherwise, in my opinion, you should just always use something like Inertia or Livewire, because your life will be much much easier.
>I think a lot of SPA consuming Laravel stuff, if it's not being forced upon you, it's sort of people don't feel cool unless they're building it that way, but, honestly, it's just a nightmare.
What do you think?
If you have built SPAs separately with Laravel API, are you switching to Livewire/Inertia now? Or maybe you have the reasons to disagree with Taylor and keep building it that way?
Personally, I agree with Taylor, it's much quicker to build an app that is just Laravel and then put in Livewire where the actual dynamic modern UX without page refresh is needed, than building the whole architecture on Vue Router, with all complexity included.