Michael Cruden
 · Seamless Technology Integration

Replacing Firebase with Supabase

Database & APIs

I have an app that is almost functional. For a variety of reasons, I started to shift my attention to Supabase. I see that it handles storage and auth as well. It seems like a complete replacement.

Is there any reason to leave Firebase connected at all?

My thought was, at least for now, to disconnect it and ensure that it breaks all the existing functions cleanly. Essentially, while testing, I might not accidentally thing something is working from Supabase when it is actually hitting against an older reference that I am depreciating.

Perhaps after this I would turn it back on. However, I think this is a good approach for the moment. I saved the project before ripping into it of course.

This process is also allowing me to refine the database schema. An example of this is I just broke out the user table into a public and private one. I won't need that for go to market, but long term I see where this may be useful, so it is already in place. Made a few refinements on the way.

Had to pick up some info on datatypes. After reading the docs, it seems text and numeric are the ones you use the most (there are a few very similar options in there). For example, their docs say the decimal and numeric are the same thing. Odd but ok..

This is the FF video I am following to get going.
https://www.youtube.com/watch?v=tL-sLPfWzVE&t=515s

What have you tried so far?

Learning Supabase

Did you check FlutterFlow's Documentation for this topic?
Yes