Filament for admin and inertia + Vue for client frontend, any complications?
Hello, I am thinking about running Filament for the admin frontend, and inertia + Vue for the client frontend built with Vite for an SPA.
Before I make the final call on this before starting developing the app, I would like to know if there would be any complications running this stack. Is it common practice to do this, or would it be better for me to choose an admin frontend that is running inertia + Vue as well?
My worries are that I would need to use Vite for the client frontend, and maybe Laravel mix for the admin frontend. And maybe there is something I have missed due to this being my first filament project.
Any advice is highly appreciated!
Thank you!
3 Replies
On my previous project, we were running the VILT stack on the front-end while using Filament for the Admin Panel. It's a massive application, so we've likely covered most if not all of the possible edge cases, and we had absolutely no issue with the two conflicting.
The only downsides are that now the product's developers need to know two stacks (Vue + Inertia & TALL) and that in some cases you may have to write double the code (one implementation in Filament and one in Vue + Inertia). I will say that, in every practical way, using Filament for the admin panel was one of the best decisions that our team made for that product. We were able to continue using Vue + Inertia on the front-end which the client and their developers were comfortable with, but we were also able to build out previously non-existent Admin panel functionality with Filament. None of the devs (who had never previously touched TALL stack) had much of a problem adapting.
Obviously, your mileage may vary depending on the project and development team, but for us, it was a MASSIVE win. Big enough that the CEO called out Filament specifically during their end of the year company all-hands meeting 😆
Thank you, that makes me more calm about it.
Could you elaborate on why you would need to write double the cod, when using filament for admin operations and Inertia + Vue in the client frontend?
I mean, doesn't Inertia + Vue just use the data from the database, that has been added with Filament, roughly speaking?
And did your project need to build any js or css for the Filament panel? Because one of my concerns is needing to build for both TALL and VILT in the same project.
Yeah, I should have been a little more specific about that. In our application, there were a handful of screens that needed essentially that same exact table logic in the Admin panel and in the client application. The only difference is that the client application was tenant-ed and the Admin panel was not. Because of that, in those places we had to write code to make a table in VILT and a table in Filament (TALL). Definitely not the end of the world at all, but something to note.
We did not need to build any JS or CSS for the Filament panel, but there shouldn't be any complications for having to do so.