Supabase + BuildShip = Truly UNBEATABLE Combo! 

You're right, we can already do all that was shown in the video with database triggers in supabase

Great question, i personally had some issues when using triggers made in supabase when trigger actions are initiated from flutter flow app actions, the triggers made in supabase work well when trigger actions are made manually in supabase but when they are automatically from external source (such as flutter flow for this instance) those in-built supabase triggers seem not to work., and even the flutter flow action chain stops. Using buildship seems to fix that error for me. Though i am not sure why.

I would only use for workflows which can not be done directly in supabase with supabase function and triggers. Buildship can be very expensive and makes you dependent if the service shutes down all is down.

Yes i see the same, i have triggers in supabase, also complex functions callled from customactions so i don“t need API calls. I don‘t see why i should use buildship and pay. It is ok if you need workflow outside the databese like sending emails…

Yes it could

Or can just in the app also put the data on the logs table…

But I guess as a prof of concept is interesting

Buildship isn't a database and does not have that functionality.

I would stay away from firebase like it was the plague. Sure, it's full featured, but can get very expensive very quickly. Also, do yourself a favour and do a google search about firebase bill shock. Google sneakily removed the ability to limit usage on paid plans, so if god forbid your app gets attacked or you mistakenly have errors in your app that case lots of usage, you'll be on the hook for tens of thousands of dollars in fees. Ultimately it's up to you, but supabase is the only option I'd go with.

They have a new one? I will check, thanks!

@@jamesnocode Thanks! Supabase renewed the logo a few years ago. The new one looks very similar, but it's a bit thicker.

Coding is 20th century. Everything should be no-code already.

I don't know, I can see going either way. If you fully leverage large language model powered resources, you should be able to build a useful and safe product. Then build a cash flow with it. Then hire an extremely experienced software engineer to refine the product.