Unless you go bare metal, you never escape that, whatever provider you use, with supabase or without

Would love to see a video how to self host suipabase in docker container.

@@cristianbilu you can self-host supabase with your own metal, also every feature or product on supabase in open-source.

Appreciate it, I certainly hope so lol

Would work perfectly. Both would fill the role of BE REST endpoints, I just find supabase a bit more convenient

Great question!

Supabase's SDK has decent image transformation for MVP, in the future we will probably use a more advanced provider like cloudinary supabase.com/docs/guides/storage/image-transformations

I jumped into react native off of the recommendations of my co-workers (they HATE flutter). So far the dev experience has been great, and expo is seriously absurdly powerful. However building to the app store continues to be miserable (I did some mobile game dev a few years ago, could be a fun story for the channel sometime). I much prefer web b/b in mobile you are abstracted so far up, that my build errors are 10,000 c++ traces that are meaningless to me in some podfile that has nothing to do with my code.

From a productivity point of view, I honestly don't think there is currently a better combo for app development than FlutterFlow with Supabase. These are real development tools, focused on productivity.

Through my university, it has been awesome working with a designer and product guy lol

Row level security rules supabase.com/docs/guides/auth/row-level-security

with supabase you are not actually exposing the DB credentials on the client, the way they achieve an "INSERT" directly from the client is because there is an API gateway (kong) in front of another product called postgREST, what postgREST does is that it exposes/maps your models in REST routes, now after postgREST evaluates the request, it tries to execute the actual SQL code and postgres (the actual DB) will now evaluate and enforce RLS rules that were defined by you before doing the operation. That's how you stay safe.

SQL and open source

Congrats on Blok btw 🎉

Lucia + planetscale or turso

@@bmdavis419 thank you, this is very valuable to me

Yeah I was wondering the same thing… Is the issue performance, latency, or what?

This would 100% work, but then I would still have to make HTTP requests to the server instead of just running DB queries on the FE which massively speeds up development

@@bmdavis419 but writing db queries from frontend is considered a huge security risk na, so better to have db calls in the backend. And since you are handling both frontend and backend, how writing backend calls will hamper development speed?

The core reason is that we need it on the App Store. Our target market is gonna have zero clue what a PWA is and we will never be able to grow

i'll give my 2 cents, PWAs don't feel native and whenever a user opens any website, he doesn't think of good experience because there is hardly any good experience on the web, relatively compared to mobile apps, the user doesn't care if its a PWA, its still a website!, but for mobile apps, good experience is expected from the get-go, a user will immediately notice and judge your entire company based on how good your app is, so yeah...

@@abdirahmanni agree, also with app you are kinda required to do notifications and other stuff which can be pain in the ass

@@andrijaoreskovic386 i agree but money speaks, its just what it is man, i cant help but implement it, i wish money grew on trees! 😆

Have not set any of that up yet but it easily could, at the end of the day it really is just postgres and some edge functions

Native wind: www.nativewind.dev/overview/

@@bmdavis419 Thanks

Its not quite at 1.0 yet, and the reality is that Supabase has more features, a bigger team, and a much bigger ecosystem behind it. This is a pretty serious project, and realistically I'm just betting on the bigger more mature tech here

Jetbrains mono nerd font

I already have years of react experience and we want to make it cross platform

U can use it on the server, and it works great (see the deep dive for a full open source app example), I just prefer the other options

@@bmdavis419 I mean, yeah. I've been loving drizzle with just a DB. But I don't actually see a significant negative to using supabase as described in your video. It basically looks like drizzle and I don't feel you articulated how it's significantly different in the video. You made a great case why you should use SB for a mobile app, but said little in the way of why one shouldn't use it for a SK app.

In your production apps, what were the other options you would use in a nextjs application?@@bmdavis419

Not at 1.0 yet, and supabase just has more features/power

www.youtube.com/@bmdavis419/about

Hi there sir ben, thankyou for interacting with me. I'm sorry to brought this up but I'm having difficulties to find your email here in your channel . I can't find your email address, can u type it here ? Thanks .

​@@bmdavis419i already emailed you sir. Thanks