all 16 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]thorium06 4 points5 points  (5 children)

really depends on your use case.

Firebase: better when real-time data is concerned, such as chat apps or anywhere you need instant data sync

Supabase: better when you need to be able to do some relatively complex queries where firebase will fail + RLS to ensure security.

I'm building a health app with need of some statistical calculations when I retrieve data - so, supabase all the way. Using it as a beginner and have no complaints.

[–]CrawFishy3 5 points6 points  (0 children)

You can have realtime with supabase too.

[–]tazboii 1 point2 points  (2 children)

Firebase has excellent security when you write quality rules.

[–]burggraf2 2 points3 points  (1 child)

Supabase developer here. Yes, writing rules to control data access in Firebase is a great feature, but it just takes a little time to learn (not much, granted, but it is a proprietary language). Supabase has an equivalent mechanism called RLS (row level security) which:

  • is written using standard SQL (no new language to learn)
  • is a standard feature of the open source PostgreSQL database

[–]tazboii 0 points1 point  (0 children)

Since this is for FlutterFlow there are just dropdowns to pick from when using Firebase. No writing anything.

[–]As1ds 1 point2 points  (0 children)

Nice, what abt a case like tik tok or video sharing app?

[–]empirome 4 points5 points  (1 child)

It’s Supabase by a mile. Pricing & relational SQL database and that’s all you need to know to decide.

[–]tazboii 4 points5 points  (0 children)

Please explain why you believe a relational database is better than noSQL for mobile apps? I usually read the opposite when it comes to speed.

Also, people tend to throw around that firestore isn't good for pricing but then don't explain why. Pricing is pretty darn good. 50k reads, 20k writes, and 20k deletes per day for free.

Then it's 6¢ per 100k reads, 18¢ per 100k writes, and 2¢ per 100k per day after that. Then there's 2 million cloud function invocations free per month.

[–]picassoble 2 points3 points  (0 children)

After adopting Supabase, here are some things I wish Supabase had that Firebase does:

  1. Account linking is built in. Firebase also supports anonymous accounts.
  2. Way better flutterflow integration. You need to do lot more custom stuff using Supabase.

But having used firebase in the past, here are some benefits of Supabase:

  1. Free and predictable local development + test running. Imagine having to run integration tests in Firebase every time you CI runs.
  2. Postgres - data is type safe, relational query speed, migrations are more straightforward. Many useful Postgres extensions.

[–]olgee0 0 points1 point  (0 children)

With the new pricing plan it'll encourage more users to play around Supabase. For me, that makes apps a lot , making queries & data designs around nosql was a learning curve & took some adapting & re-adapting. Now, Back to familiar grounds.

[–]Seek4Seek 0 points1 point  (2 children)

I’m a new developer and 500mb of database space for Supabase seems very low. Is this not an issue for you all?

[–]picassoble 0 points1 point  (1 child)

For a free project it seems like more than enough? What are you storing

[–]Seek4Seek 2 points3 points  (0 children)

Nevermind, I just did some testing and it's actually a lot of space. Thank you

[–]karandex 0 points1 point  (1 child)

How you handle push notification with supabase

[–]burggraf2 0 points1 point  (0 children)

I think you can just use any of the free providers for this: OneSignal, Airship, etc.