4 ms·

Supabase is great - I use them now and they and would be my choice for a new project today - but I have to say I am not a huge fan of how they communicated the

Supabase is great - I use them now and they and would be my choice for a new project today - but I have to say I am not a huge fan of how they communicated the whole auth-helpers and ssr situation, and I am not the only one with this comment by a long shot. This is, I think, a part of wider issues with their documentation; it seems like whoever's doing documentation at Supabase is intelligent but stretched thin. Particularly for Sveltekit, the documentation and examples are incomplete, there isn't any guide to migration or how to modify your code, and if you Google things or follow any links or examples you quickly end up in a web of deprecated repositories where it's unclear what to do next or replace them with. One example: https://github.com/supabase-community/auth-ui https://github.com/supabase-community/auth-ui If you produce a product for developers, you really need to have 1) quality, readable documentation with an introduction that noobs and pros alike can follow, 2) multiple complete, cloneable examples on how to integrate and use your product in several different libraries, 3) obvious migration guides and timelines whenever you deprecate something. Supabase lacks all three, which is extremely frustrating and means there's always a giant caveat when I recommend them. They're still the best, it's a very powerful and impressive product, and the possibility of self-hosting is amazing.

kiwicopple 3y ago
> They're still the best, it's a very powerful and impressive product first, thanks for these kind words - it's encouraging (as a maintainer, not just a team member) when we know we're on the right track sorry about the frustrations, especially around the ssr/auth-helpers. We definitely could have handled that migration better (and the comms in particular). To address some of your other points: > 2) multiple complete, cloneable examples on how to integrate and use your product in several different libraries Yesterday we made it even easier to do just that with "supabase bootstrap"[0]. We'll be adding all of our quickstarts[1] which cover most of the key (frontend) frameworks > 3) obvious migration guides and timelines whenever you deprecate something Agreed. We actually developed this internally after the auth-helpers/ssr. We'll do better in the future. [0] bootstrap: https://supabase.com/blog/supabase-bootstrap https://supabase.com/blog/supabase-bootstrap [1] quickstarts: https://supabase.com/docs/guides/getting-started https://supabase.com/docs/guides/getting-started

kiwicopple 3y ago

> They're still the best, it's a very powerful and impressive product first, thanks for these kind words - it's encouraging (as a maintainer, not just a team member) when we know we're on the right track sorry about the frustrations, especially around the ssr/auth-helpers. We definitely could have handled that migration better (and the comms in particular). To address some of your other points: > 2) multiple complete, cloneable examples on how to integrate and use your product in several different libraries Yesterday we made it even easier to do just that with "supabase bootstrap"[0]. We'll be adding all of our quickstarts[1] which cover most of the key (frontend) frameworks > 3) obvious migration guides and timelines whenever you deprecate something Agreed. We actually developed this internally after the auth-helpers/ssr. We'll do better in the future. [0] bootstrap: https://supabase.com/blog/supabase-bootstrap https://supabase.com/blog/supabase-bootstrap [1] quickstarts: https://supabase.com/docs/guides/getting-started https://supabase.com/docs/guides/getting-started