What is Ionicons and what are its top alternatives?
Top Alternatives to Ionicons
React
Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...
Font Awesome
You can get vector icons and social logos on your website with it. It is a font that's made up of symbols, icons, or pictograms that you can use in a webpage, just like a font. ...
Material-UI
MUI (formerly Material-UI) is the React UI library you always wanted. Follow your own design system, or start with Material Design. ...
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. ...
ElementUI
It is not focused on Mobile development, mainly because it lacks responsiveness on mobile WebViews. ...
Feathers
Build mobile & desktop games and apps with fully-skinnable UI controls. It aims for buttery smooth performance based on the philosophy that cross-platform UI kits shouldn't sacrifice one of the most important benefits of native development. ...
Ionicons alternatives & related posts
- Components760
- Virtual dom652
- Performance563
- Simplicity486
- Composable436
- Data flow175
- Declarative159
- Isn't an mvc framework124
- Reactive updates113
- Explicit app state111
- JSX32
- Learn once, write everywhere23
- Uni-directional data flow19
- Easy to Use16
- Works great with Flux Architecture14
- Great perfomance10
- Built by Facebook8
- Javascript7
- TypeScript support5
- Speed5
- Feels like the 90s4
- Scalable4
- Easy to start4
- Awesome4
- Fancy third party tools3
- Hooks3
- Functional3
- Server side views3
- Props3
- Rich ecosystem2
- Obama2
- Very gentle learning curve2
- Has functional components2
- Simple2
- Closer to standard JavaScript and HTML than others2
- Super easy2
- Has arrow functions2
- Strong Community2
- Great migration pathway for older systems2
- SSR2
- Fast evolving2
- Simple, easy to reason about and makes you productive2
- Excellent Documentation2
- Scales super well2
- Just the View of MVC2
- Server Side Rendering2
- Cross-platform2
- Fragments1
- Start simple1
- Every decision architecture wise makes sense1
- Permissively-licensed1
- Beautiful and Neat Component Management1
- Sdfsdfsdf1
- Allows creating single page applications1
- Split your UI into components with one true state1
- Sharable1
- Requires discipline to keep architecture organized35
- No predefined way to structure your app23
- Need to be familiar with lots of third party packages21
- JSX8
- Not enterprise friendly7
- One-way binding only4
- State consistency with backend neglected2
- Bad Documentation2
related React posts
.NET Core
Angular CLI
React
MongoDB
Flutter
React Native
Postman
Markdown
Visual Studio CodeI am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.
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.
- CDN7
- CSS Styling5
- Open source3
- Easy Upgrades0
- Auto-accessibility (A11y)0
- API0
related Font Awesome posts
Vuetify
AngularJSReact
NativeScript-Vue
Font Awesome
Google Fonts
Jest
Prettier
TSLint
ESLint
GraphiQL
GraphQL
Apollo
TypeScript
JavaScript
Babel
CSS 3
HTML5
Sass
Webpack
vuex
Vue Router
Vue CLI
Nuxt.js
Vue.jsOur whole Vue.js frontend stack (incl. SSR) consists of the following tools:
- Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
- Vue Styleguidist as our style guide and pool of developed Vue.js components
- Vuetify as Material Component Framework (for fast app development)
- TypeScript as programming language
- Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
- ESLint, TSLint and Prettier for coding style and code analyzes
- Jest as testing framework
- Google Fonts and Font Awesome for typography and icon toolkit
- NativeScript-Vue for mobile development
The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:
- Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
- Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
- Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
- Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
- Large scaling. Vue.js can help to develop pretty large reusable templates.
- Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
- React115
- Material Design76
- Ui components49
- CSS framework25
- Component20
- Looks great12
- Responsive10
- Good documentation10
- LESS9
- Open source7
- Code examples6
- Ui component5
- Flexible5
- JSS4
- Very accessible3
- Angular3
- Supports old browsers out of the box3
- Designed for Server Side Rendering2
- Interface2
- Fun2
- LADO2
- Easy to work with1
- Barev Arman1
- Asdasd1
- 5550
- Hard to learn. Bad documentation27
- Hard to customize22
- Hard to understand Docs18
- Bad performance6
- Extra library needed for date/time pickers5
- For editable table component need to use material-table5
- Long Code5
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?
- Lots of components39
- Polished and enterprisey look and feel30
- TypeScript20
- Easy to integrate18
- Es6 support18
- Beautiful and solid16
- Beautifully Animated Components15
- Quick Release rhythm14
- Great documentation13
- Typescript support12
- Short Code10
- Less17
- Large File Size8
- Close7
- Poor accessibility support4
- Gago1
- Sdf1
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 :)
Hi, I start building an admin dashboard with next.js and looking for a frontend framework ( components ready ). So I end up with Ant Design and Material-UI, but I never built a project with these two.
Here is a list of my requirements.
- Good documentation.
- easy CRUD ( date picker and date range picker bundled )
- built-in multi-lang feature or Great 3rd library support
- Admin dashboard template
- well code maintenance
Which is better for the long run?
- Typescript Support4
- Barev Arman1
- Accessibility1
- B0
related Chakra UI posts
- Large transfer size2
related DevExtreme posts
- Avaliable for other frontend frameworks too4
- Wqas0
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 :)