Moving from Livewire to Vue.js + API

[indigo plaza]

My first question is, why do you think moving to Vue with a Laravel API will slow your backend development skills down?

[jolly fjord]

As I mentioned, I’m still exploring the Laravel ecosystem. While I can build functional applications, I'm fully aware that my code needs improvement in areas like SRP, reducing duplication, and query optimization. Since I have very little experience with Vue, I’d need to invest significant time into it, which I fear might stall my progress on the backend - my primary focus. When I look at mentioned projects like the vehicle maintenance log or the URL shortener, the backend logic seems relatively straightforward, but I’m concerned that the frontend will consume a disproportionate amount of my time. I’m trying to figure out how to ease into Vue gradually without getting bogged down in the details for now, so that my Laravel learning curve doesn't suffer.

I would probably try Inertia.js first, but since both my engineering thesis and my upcoming internship specifically require building a decoupled API, I’d rather invest my time in that workflow now. It makes more sense to 'bite the bullet' and get comfortable with the API + Vue setup before I have to deliver my degree project or start professional work.

I'm debating whether I should stick with Laravel + Livewire for a while longer to finish these projects and focus on mastering clean code and best practices, or if I should just dive straight into a proper 'API-first' approach and then face the challenge of learning Vue.js.

[indigo plaza]

I would have suggested Inertia JS- but like you mentioned you need it to be completely decoupled. If I were in your position, I would move towards Vue and Laravel API- but focus on the API side first. Use something like Postman or write TDD tests to ensure the backend has best practices, then move onto using Vue for the frontend, since you're completely new to it. With 3 months, that isn't a lot of time to get comfortable with a decoupled architecture like this.

Also, if you need to deploy a decoupled API and frontend, you'll need time to learn that as well

[jolly fjord]

I’m not starting my engineering thesis and project preparation for another three months, so my main goal right now is to grasp the basics and learn how to navigate the ecosystem efficiently. In total, I’ll have nearly a year to complete the thesis, so I think that should be enough time to get it done. Also, deployment won't be necessary at the beginning.

[indigo plaza]

If the end goal is that you need a decoupled api and frontend, thats where I would start now 🙂 I don't think there's much advantage continuing with livewire unless you plan on using it in the future- I also wouldn't say livewire is heavily used in industry, so you'll get enough benefit from just writing PHP over livewire for the moment regardless

[jolly fjord]

I'm going to follow that path. Thanks! One last thing - is Vue the right call for a backend-focused dev? I chose it because I read that it’s faster for shipping projects than React or Angular, with less boilerplate and a more intuitive syntax that feels like "regular" HTML and JavaScript.

[indigo plaza]

To be honest, if your plan in the future is to be a backend dev, I would use choose Vue because (from experience) it seems easier for people who haven't used a frontend library like React, Vue, or Angular before. If your question was for a fullstack, I'd say React as it's the more popular one. No problem!

[jolly fjord]

Thanks! Have a nice day