Tell me a little bit about yourself and what kind of team you're working on?
I work on mobile pretty much technical and engineering over there. We're really small team actually, and we're based out of Singapore. So yeah, in the past, something more relevant to what you guys are doing is that we actually moved from Firebase.
At the same time, we relaunched Mobbin at time for that. And the reason for that migration was because we hit some limitations on Firebase really while building that new iteration of Mobbin.design and we made the painful decision to drop whatever we were doing and start migrating over to Supabase.
What was the first thing that made your team start talking about that switch?
It was really indexing, right? We have a very read, maybe a kind of application, and so indexing is really important. The thing about Firebase is that if you want to do queries with relationships, you have to do a lot of round trips or you got to try to walk around the limitations of the indexing, which is actually really limited that there are some height limitations on indexing.
For example, there's fixed. Which is a bit spaced on you, you can have as many indexes, like as long as you can just scale the underlying storage space on. Yeah.
Was there something that triggered that switch to move it over?
We hit a hard constraint, that we couldn't work around on Firebase. We were trying to build a better search experience. If you look at the new Mobbin, you can have very complex compound queries. You can look for screens that have buttons, sliders, and are also part of a sign-up flow, part of our settings flow. You can do all sorts of crazy complex operations, which as a designer is what you want to do. You want to filter by category?
What are all the finance apps doing for the login flow when they have a certain element on the screen? But with Firebase we, couldn't going to do that
. How long was it before you decided to make the switch? How long before you said "we should do this" to "we actually are going to do this".