[rohan_]

supabase has the most schizoid brand. They should just embrace the fact that mobile devs don't want to do backend for their crud app rather than trying to be the "everything backend".

why are they releasing a web component library when React Native doesn't even have a decent UI library? Like who are supabase's customers again??

[kiwicopple]

[supabase ceo]

Despite the title "UI library", this is more like a "component registry" for developers to bootstrap their applications and it will work for everything from Web & Mobile, to database scaffolding. Perhaps some poor naming/positioning on our part.

If you aren't familiar with shadcn, it works by dumping a bunch of files into your application which you can modify at your leisure. This is a different from something the "Bootstrap" approach where you could only do minimal tweaks to the theming.

[BoorishBears]

The distribution person in me commends you for cashing in on the "component registry" hype in such a creative way. And that's not a backhanded use of the word creative: the moment it clicked was great, really just a smart application of something people are hyped about right now!

But the developer in me, who realizes how bad we are at design realizes shadcn/ui is terrible for 99% of people using it. They don't have a design system, don't know what that even means, and their sinful hands should not be tweaking any UI libraries, at most being limited to modifying a rich set of theme tokens that force consistency... not touching individual components or copying in random cruft with hard coded gaps between elements.

And so for all that (and also tl;dr) I wish you'd have just shipped actual versioned, buttoned-up components that are well thought out and themeable through tokens, just like your existing auth UI.

You could have even made the default theme shadcn-like to satisfy all the people lying to themselves that one day they'll actually modify that ui folder.