So much trouble with Supabase - switch to Firebase? (with UPDATE)

[ykdojo]

Hey everyone!

I've done everything I could do today with Supabase to make it work with the frontend-backend connections, but I'm having a LOT of trouble with it.

More details: #108

Anyway, I'm now seriously considering switching to Firebase.

It's supposedly more mature, better documented, and it's more battle-tested if I understand it correctly.

Any thoughts?

I'm thinking of playing around with it sometime soon to see if I can get it to work.

With it, NextAuth might be a good option, too.

UPDATE:

Based on my convo with @subhoghoshX below, I was able to resolve this issue! I'm thinking perhaps we should give it a try a bit more... Let's see how it goes.

[RakeshSangem]

I have worked with Firebase firestore. It's blazingly fast and documentation is top notch in my opinion.

[subhoghoshX]

I didn't know that you were facing issues with Supabase. I thought it was straightforward to work with once you figure out the policies. Could you please elaborate on what issues you're facing?

[subhoghoshX]

Yeah definitely. Or we can just use loaders. Using loaders is a pretty common pattern.

[ykdojo]

Interesting. Any reference article, post or site we can look at for that?

[subhoghoshX]

Thanks for asking. I never thought of doing research into it. I just always liked them by instinct.

Here by loaders, I also mean skeleton loaders as well. I personally prefer skeletons much more than spinners. There are many websites using them like Supabase, LeetCode, Quora, YouTube, etc.

I found this article and this talk to be quite interesting. And this Reddit post as well.

[ykdojo]

Thanks! The skeleton loader in the Reddit post does look really cool

[subhoghoshX]

Here is an example skeleton loader implemented with pure tailwindcss. We can do something like this in some parts of the UI.