Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hey all, I have been trying to decide which way to go for development on my main project in terms of how the SPA functionality will work on the frontend.
My options are using Splade with Blade or using Inertia with Vue.
I know Splade is only very very new & hasn't had as much exposure yet, but has anyone had a chance to play around with it & what is it like compared to Inertia?
Which one would you use if you were going to make a website, let's say with all the features that Laracasts has (for example)?
Thanks in advance, I value your opinions.
I would first choose between Vue/React or Blade. It isn't about Inertia or Splade. (good rhythm 😅)
For a website like Laracasts I would choose Inertia. And actually it's built using Inertia and Vue.
I didn't try Splade, but as I mentioned I would choose Inertia because it's better for me to build the feature here using Vue not Blade.
I am aware the choice is between blade & Vue. Until Splade was released, I wasn’t aware there was an option (outside of livewire) for a package that could handle SPA reactivity within blade in the same way inertia does.
Maybe on of the presenters will do a video on Splade as it is an extremely new resource that the community (it seems) is mostly unaware of at this point.
I'm facing a similar dilemma. I've been using Livewire for a while, but have been running into certain limitations and annoyances that have compelled me to find another option.
I've been experimenting with InertiaJS & Vue, which has a lot of benefits for me. But It would also be very helpful to be able to continue to use the Blade components I already have as I phase out Livewire and replace with Vue.
With Inertia, I can use Blade templates only up until I mount my Vue app. I like that Splade allows composing Blade and Vue markup together. This would allow me to keep my existing Blade components and slowly replace them with Vue equivalents.
But I'm apprehensive due to security and performance concerns. Splade is newer, has a smaller community, and is more opinionated than Inertia + Vue.
@SleeplessDev if you go with inertia, you could have some routes use regular laravel routes with blade views. You would need to create the maintain the menu and such twice while migrating, but I assume that manageble. I use a mix of it in my app
@SleeplessDev Splade is more secure out of the box than Inertia. You don't send to client everything by default. It's just like using plain PHP with database queries. With Inertia you have to be more careful and think about it all the time or use API resources.
I have tried both Inertia and Splade.
With Splade you get the Laravel niceties out of the box - no need to hack the code or reinvent the wheel if something doesn't work ok - and tbh it's quite common.
I don't want to write my app "twice" - once in JavaScript and once in PHP as it is with Inertia. There is a lot of duplication and non-standard solutions to things that are super elegant and straight-forward in Splade.
I will give you a real world example.
I needed to use Laravel Localized Routes - with Splade it works out of the box as if you are using a normal Laravel.
But I haven't been able to make it work with Inertia. Perhaps it can be done but the "plumbing" and extra coding necessary is not worth the time if I can use something that works without any hacks out of the box as is the case of Laravel Localized Routes with Splade.
Unfortunately, localized routes are important for my projects because I am not from the US and in my country we speak multiple languages.
This thing alone is a reason for me.
The other is the authors. The Splade author is super enthusiastic and active about Splade. The Inertia author just passed the project to the Laravel team - so I think that says a lot about the enthusiasm.
Another huge thing is out of the box stuff I use daily. This is so UNDERRATED.
You can see that the author of Splade has done a ton of real-life projects based on the stuff he offers out of the box in Splade. There is no to very little things I have to do from scratch when using Splade. The most common things are there ready to be used and customized.
In those no-to-very-rare instances of me wanting a specific JS functionality I do create a Vue component but that's rare.
I wouldn't go back to Inertia after using Splade.
@Aeuais Thanks for sharing your impressions about Splade. As far as you know, are there any limitations using Splade related to Single Application Pages? I mean "something which can't be done / it's veeery hard to accomplish using Splade"
@Aeuais I am starting a project today with Splade, though I've known about it for like a year now.
Thanks for all your replies.
I have done a lot of research now & looking at the Splade roadmap I am hopeful that Splade might get inbuilt (out of the box) integration into Laravel (like Livewire & Inertia), as it is a powerful & in my opinion better integrated to the fundamentals of Laravel than Inertia is. It has bundled into the framework other Javascript libraries (Choice.js) & UI components that are excellent to use.
I look forward to seeing what will happen with Splade in the next few months.
Please or to participate in this conversation.