The BIG Problem With Shadcn UI…
I’m a big fan of Shadcn UI, it’s helped me ship projects 10x faster while keeping them consistent, beautiful, and most importantly, accessible. But here’s the thing: now where Shadcn UI is maturing, I’ve realized that using it might actually be a big mistake. From fundamental design choices, to the dependencies under the hood that aren’t well-maintained, to limited customization options, and the lack of real accountability from the teams behind these projects, all of these issues raise concerns. What I am trying to say is that In the long run, Shadcn UI might be a bigger risk for us web developers than most people think. Watch this video to learn why!
📸 Screen Recording Software: https://dub.sh/eDa47SO
🔒 My favorite Auth Solution: https://dub.sh/xeU8r3v
🌍 My Website: https://marshalcode.com/
👋🏻 Discord: / discord
✅ Follow me on X: https://x.com/janmarshaldev
📧 Business ONLY: [email protected]
Timestamps:
00:00 Intro
00:47 What Shadcn UI fundamentally is
01:45 Broken dependencies under the hood
05:20 Why the fundamental architecture has to change
09:20 1000+ GitHub issues (bad library maintenance)
12:00 The problem with customization