What is Component Box and what are its top alternatives?
Top Alternatives to Component Box
- Material-UI
Material UI is a library of React UI components that implements Google's Material Design. ...
- Ionicons
Premium designed icons for use in web, iOS, Android, and desktop apps. Support for SVG and web font. Completely open source and MIT licensed. ...
- Ant Design
An enterprise-class UI design language and React-based implementation. Graceful UI components out of the box, base on React Component. A npm + webpack + babel + dora + dva development framework. ...
- Chakra UI
It is a simple, modular and accessible component library that gives you all the building blocks you need to build your React applications. ...
- DevExtreme
From Angular and React, to ASP.NET Core or Vue, it includes a comprehensive collection of high-performance and responsive UI widgets for use in traditional web and next-gen mobile applications. The suite ships with a feature-complete data grid, interactive charts widgets, data editors, and much more. ...
- AMP
It is an open source initiative that makes it easy for publishers to create mobile-friendly content once and have it load instantly everywhere. ...
- ElementUI
It is not focused on Mobile development, mainly because it lacks responsiveness on mobile WebViews. ...
- Tailwind UI
Over 400+ professionally designed, fully responsive, expertly crafted component examples you can drop into your Tailwind projects and customize to your heart’s content. ...
Component Box alternatives & related posts
Material-UI
- React138
- Material Design82
- Ui components60
- CSS framework29
- Component24
- Looks great14
- Responsive12
- Good documentation12
- LESS9
- Open source7
- Ui component7
- Flexible6
- Code examples6
- JSS5
- Angular3
- Supports old browsers out of the box3
- Fun3
- Very accessible3
- Designed for Server Side Rendering2
- # of components2
- Interface2
- Easy to work with1
- Support for multiple styling systems1
- Typescript support1
- Css1
- Accessibility1
- Hard to learn. Bad documentation34
- Hard to customize27
- Hard to understand Docs20
- Bad performance7
- Extra library needed for date/time pickers6
- For editable table component need to use material-table6
- Typescript Support1
- # of components0
related Material-UI posts
I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.
A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.
In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.
If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.
My React website is a simple 5-pager that attaches to a database to store and display registrations and other data. The user (small user base) can change any form elements, but I don't need theme-ing, though that would be fun for the user. reactstrap/react-bootstrap built on Bootstrap 4 sounds dated. I am familiar with reactstrap, but a friend said to try Material-UI. The thought of learning it is interesting, but somehow I think it might be overkill. So... reactstrap, react-bootstrap, or Material UI, which should I use?
- Ui Components2
- Icons2
- Looks Amazing1
related Ionicons posts
- Lots of components47
- Polished and enterprisey look and feel33
- TypeScript21
- Easy to integrate20
- Es6 support18
- Typescript support17
- Beautiful and solid17
- Beautifully Animated Components16
- Quick Release rhythm15
- Great documentation14
- Easy to customize Forms2
- Opensource and free of cost1
- Less24
- Large File Size10
- Poor accessibility support4
- Dangerous to use as a base in component libraries3
related Ant Design posts
Hi there!
I just want to have a simple poll/vote...
If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:
1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.
2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.
Your advice would help a lot! Thanks in advance :)
Hello, A question to frontend developers. I am a beginner on frontend.
I am building a UI for my company to replace old legacy one with React and this question is about choosing how to apply design to it.
I have Tailwind CSS on one hand and Ant Design on the other (I didnt like mui and Bootstrap doesn't seem to have enterprise components as ant) As far as I understand, tailwind is great. It allows me to literally build an application without touching the css but I have to build my own react components with it. Ant design or mantine has ready to use components which I can use and rapidly build my application.
My question is, is it the right approach to: - Use a component framework for now and replace legacy app. - Introduce tailwind later when I have a frontend resource in hand and then build own component library
Thank you.
- Typescript Support7
- Responsiveness4
- Good documentation3
- Accessibility3
- Styling system1
- # of components1
- Inflexible token structure1
- Hard to customise1
related Chakra UI posts
- Large transfer size4
related DevExtreme posts
related AMP posts
- Avaliable for other frontend frameworks too8
related ElementUI posts
Hi there!
I just want to have a simple poll/vote...
If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:
1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.
2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.
Your advice would help a lot! Thanks in advance :)