[bgorman]

Unfortunately this is the wrong team. I have worked on several Postgres full stack applications over the past few years, and I really wanted Supabase to work, the idea sounded great. The JavaScript SDK, the documentation for getting started, and the user interface are all horrible/half-baked. Instead of speeding up my development, Supabase lead me to waste hours in confusion. It is easier to roll your own auth and setup your own database than use Supabase unfortunately.

For a product whose whole purpose is to enable developers to move faster, the product misses the mark completely. If I were CEO I would shift all resources to fixing the UI and SDK.

I would guess out of all the people who have signed up, less than 1% have actually made a “working” frontend.

[yesimahuman]

"Horrible" and "half-baked" don't describe my experience using Supabase at all. Yes, they have work to do. Yes, the documentation is lacking in certain areas. No, this round doesn't indicate they've magically got it all figured out.

[kiwicopple]

> If I were CEO I would shift all resources to fixing the UI and SDK

I'm the CEO :)

Thanks for the feedback. I would love to hear any specifics - where you got stuck and which parts of the UI/SDK we can improve. My email is in my profile.

We know we have a lot more to do, and we love building based on user feedback.

[onelovetwo]

Congrats, hopefully this means an iOS sdk soon? :D

[kiwicopple]

definitely. We need better mobile support (beyond RN/Expo/Flutter)

[ignoramous]

> Unfortunately this is the wrong team.

Ouch. I don't get those vibes from them, but it could also mean that building a FOSS platform like supabase is terribly hard?

> For a product whose whole purpose is to enable developers to move faster, the product misses the mark completely.

The good news is, they've now got $80m to hire top talent and figure this out over the course of next few years.

[kiwicopple]

I agree! I think our team is great

But then again, the harsh feedback is usually has the most truth. I'll share it with the team - we are always looking to improve.

[searchableguy]

While I don't agree with supabase not being useful, I agree that their getStarted documentation could use some work.

I've faced many issues with the twitter auth. For example, you need to enable accessing email via an additional option on twitter developer dashboard for it to work with supabase. It wasn't documented. I've faced bugs which appeared and disappeared between upgrading supabase instance (You can have different instance version if you created a new application in the middle of beta).

The real time doesn't work until you enable the sync on the supabase dashboard which was not apparent to me. There are bunch of oddities with how policies and realtime work.

The CLI has gone through multiple confusing iteration.

I would still recommend supabase to anyone though. Solid despite rough edges.

[wenbo]

Supabase dev and the maintainer of Supabase Realtime here!

> The real time doesn't work until you enable the sync on the supabase dashboard which was not apparent to me.

Thanks for the feedback! I think you're right and we can do a better job of exposing this so it's more apparent for everyone.

> There are bunch of oddities with how policies and realtime work.

Would love to hear more about the oddities! Realtime works with Postgres RLS policies so there should be nothing odd about it. Set up your policies and Realtime works accordingly.