What Svelte UI Library Should You Use?
Video Statistics and Information
Channel: Joy of Code
Views: 28,477
Rating: undefined out of 5
Keywords: svelte, sveltekit, ui components, ui library
Id: O0mNU0maItY
Channel Id: undefined
Length: 18min 40sec (1120 seconds)
Published: Fri Dec 02 2022
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
Svelte Headless UI should get some new PRs merged soon based on some comments u/ryangossiaux posted in the repo less than a week ago. He stepped away from the project for a bit after putting in a tremendous amount of work into it, and as someone who has used his library alongside Tailwinds UI on a number of projects, Iβm super thankful for what heβs managed to do, and I hope that more people from the community will help support the project.
Hey, everyone.
I'm coming here from React-land (and have 6+ years of experience with it of the 20+ in software/web dev).
In my opinion, the Svelte UI ecosystem still lacks a full-fledged library that facilitates building applications with "real-life" user input: I'm primarily referring to components such as autocomplete/select and date/time pickers. I know there are stand-alone options out there and one could, in theory, visually integrate them into a chosen UI library, but I'd wish we'd have something like Blueprint.js, Ant Design or Mantine UI for React.
The only one that comes close, as far as I've discovered, is Carbon. But for some reason I really, really don't like their design system.
This is - IMO - the single big showstopper when considering Svete/SvelteKit for a new, greenfield project.
Just my 2c.
Disclaimer: I may be a bit biased. I'm the author of a number of open-source projects in React - some of them front-end related, such as Mantine DataTable, but I've also built tRPC-SvelteKit... because I f*cking loved Svelte from the moment I first discovered it!
So, I know the ecosystem needs a bit of time to catch up, and I know there's a lot of work involved in bringing a new UI library to life; did my own share. But unfortunately there's only so much unpaid work I can do for the benefit of the community :-)
Ionic - https://ionicsvelte.firebaseapp.com/
At first I didn't understand why people went Tailwind, because I was so new and needed components to be done for me.....
After a few months around in the frontend, I totally will root for Tailwind, once you get familiar with it, it is so remarkably easy and mobile first was new to me, but now I wouldn't love without it
I really wish Skeleton's components design and default UI themes can look a bit nicer... That's my only complain about it.
Iβm a Python developer, currently working on a web app and needing a frontend in the process. Iβm definitely not a designer and quite far away from calling myself a JS developer. Thatβs my situation.
I definitely need some help building a good looking UI. Tailwind looks cool but pairing it with svelte doesnβt seem like a match made in heaven.
I started with skeleton a few months ago and switched to daisyui after some time because a) I needed components that skeleton didnβt have at the time and b) noticed that adding a bit of logic to daisyui components to get interactive svelte components really isnβt a lot of work.
I like daisyui because it gives me the design part and I can add the functionality part exactly the way I like on top. Using prebuilt svelte components gives you the risk that they work in a way you donβt like and you cannot change much about that.
Ironically though I switched back to skeleton because a) somehow daisyui looks really ugly and unrefined to my eye after a while and b) skeleton has been gaining a lot of momentum and added a lot of stuff. Iβm mostly happy with skeleton right now.
Carbon Components
Border-radius is so 2010s π
Well this is a bummer. I hate react but I need better ui libs to switch to svelte. Angular, vue, hell, even blazor have better offerings.
Carbon components https://carbon-components-svelte.onrender.com/