---
tags: v3
---

# Component Library Bonanza

For starting a DAOHaus specific component library

## Who uses this library?
- Users are developers who are looking to build an application in the DAOhaus ecosystem. (Community Devs)
- Users are MageSmiths who are building a new v3 application, and the library (MageSmiths)
- Users are the community, who are using the UI to interact with DAOs.

### Community Dev Needs
- Fast Implemention
- Low/No styling. Already included
- Low bugs. Reliable.
- Consistent w/ other DAOhaus apps
- Easy to use.

### Magesmiths Needs.
- Low bugs. Reliable.
- Customizable enough to implement designs easily
- Low dependency
- Lean, low clutter
- Functional, testable, high composability

### User Needs
- Reliability
- Seamlessness (low flickering, twitching, etc)
- Visually appealing

## The Ideal Library

Based on the needs above, the ideal library should:
- Have a low surface area and a tight focus on reliability
- Should either be well used or exceptionally written. Community devs are two degrees removed the initial component library.
- Should be composable so community devs and code generators can quickly create template UIs without much difficulty
- Should be low level enough to handle some pretty heavy customization.
- Community devs should be able to customize without much difficulty (ex. no !imortant or heavy weighted CSS selectors)
- Load fast and doesn't bog up community apps
- Is as simple as humanly possible

## Candidates

- [reach-ui](https://reach.tech/)
- [Stiches](https://github.com/modulz/stitches)
- [reackit](https://reakit.io/docs/button/)
- [Radix](https://www.radix-ui.com/)
- [Mantine](https://mantine.dev/)
- [Styled System](https://styled-system.com/)
- mobile styling is a pain
- [Chakra](https://chakra-ui.com/)
- not low enough to handle heavy customization