#What issues have you seen with Supabase

1 messages · Page 1 of 1 (latest)

hexed needle
#
  1. Docs are almost always out of date and GitHub issues go unanswered. It's like a graveyard of lost souls (+ the docs AI bot hallucinates wrong code like crazy)
  2. Doesn't support mobile/native auth properly (e.g. expects a nonce even though Google auth doesn't send one)
  3. Bad tooling when it comes to working with auth on localhost
  4. Because docs are bad, things that should be simple (like doing cookie-based versus server-based auth versus creating your own supabaseClient for bearer auth) become incredibly painful. Too much magic / abstractions hidden away
  5. Interaction within postgres itself also becomes painful as a result (again, really bad docs) making it difficult to setup RLS or RBAC for simple scenarios

I'd just look at Supabase Auth as a v0.1 product. Clerk is more of a v3.0 product (still has rough edges of its own to be fair, and expensive af) and Auth0 is more of a v5.0 product (but expensive af)

topaz solstice
#

The biggest issues I ran into with Supabase Auth where that they keep pushing out a lot of stuff with server actions. Even though server actions are still in Alpha...

hexed needle
#

I talked w/ the CEO via DMs and mentioned they just keep pushing out new code / features before they ever ensured their core auth features were robust and functional. Makes no sense. I can't use all the shiny things if auth won't even work at the beginning of my UX / developer experience