I find fluxon ui to be the best component library for LiveView in terms of quality. Very few stylistic issues (e.g. no odd icon placements or spacing issues type of issues) and has autocomplete which a lot of component libraries tend to not have implemented, like tailwind plus. It isn’t free but worth the cost IMO.

Hi dear @arcanemachine
I wanted to mention something about MishkaChelekom. One of the features I’ve recently worked on again is that you can use any other system alongside MishkaChelekom and vice-versa. We’ve built a large number of components that don’t exist in other libraries, and unlike the stateless approaches others have introduced, our components are built with Phoenix LiveView lifecycles.

Because of this, you can use the CLI to pick and use any component you like.

Personally, I think forms are still one of our weak points and we need to dedicate a full phase to improving them. But for everything else, I believe we have enough to build any dashboard. You get a solid collection of components with extensive features, and each component becomes part of your project, giving you plenty of room for customization.

And 100% free and open-source

For all of my current endeavors (SaaS and otherwise), TailwindPlus is my go to. While it is obviously not a Liveview component framework, it’s easy enough to copy and paste the provided HTML into a Liveview component whenever you need to reuse their components more than a couple of times across the app. The components are all high quality and adapting the components to your theme is pretty easy by leveraging the Tailwind color pallette. Granted it costs money…but you get what you pay for…i.e quality looking responsive design components and layouts.

They recently introduced their web component version for some components that require JS. To be honest, this is both a blessing and a curse. On the one hand it does make it easier to use their components so long as you don’t need Liveview within the component. But if let’s say you need a form inside their modal component you may run into issues when Liveview patches the DOM. I haven’t found a good way around this at the moment…but I also only dove into the issue for just an afternoon.