Hi! I'd like your opinion on a new stack I'm experimenting with for mobile apps. I'm using Supabase for Auth and DB, which I connect to my Laravel app as the main Postgres database. Then my mobile app, built with Quasar framework, pulls its data from Supabase via Postgres functions.
This gives me the best of both worlds: a control panel that can be hosted on Laravel Cloud with hibernation and with no DB, which only admins will use (so at a very low cost!), and a frontend that connects to the same data, but in a slightly different way. This also allows me to isolate my admins (in Laravel/Filament) from my app users (in Supabase Auth) without Sanctum/JWT.
The goal of this stack is to not deal too much with CORS issues, and to enable rapid MVC development, while leveraging the strengths of Postgres (vector search, PostGIS, etc.), and to avoid having to build, test, and secure an API (although Supabase also needs to be secured, but with RLS, it's still quite simple).
What do you think?
Anonymously
How are you Trudel?
Excellent! IMO, for now the only minimal missing pieces in the starter kits are optional two-factor authentication (2FA) and API tokens (to match what Jetstream offers, as well as the Breezy plugin in Filament).
And perhaps the teams feature, but I never liked the way Jetstream did it, so it's better not to implement it if it's going to be the same...
Is Filament Panels fully compatible with Laravel 12, will the fact that Laravel uses Tailwind 4 cause problems? Would I be better off waiting before upgrading to Laravel 12 on my development project?
ok thanks, then I'll stay on Laravel 11 for that project and wait for the upcoming release of Filament.
I rather have the feeling that it's Arc who is leaving us... www.youtube.com/watch?v=1PxhTfmEyQ8