Ant Design vs Semantic UI: What are the differences?
What is Ant Design? A set of high-quality React components. 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.
What is Semantic UI? A UI Component library implemented using a set of specifications designed around natural language. Semantic empowers designers and developers by creating a shared vocabulary for UI.
"Polished and enterprisey look and feel" is the primary reason why developers consider Ant Design over the competitors, whereas "Easy to use and looks elegant" was stated as the key factor in picking Semantic UI.
Ant Design and Semantic UI are both open source tools. It seems that Ant Design with 48.6K GitHub stars and 17.2K forks on GitHub has more adoption than Semantic UI with 45.9K GitHub stars and 4.84K GitHub forks.
Snapchat, Accenture, and Reviewable are some of the popular companies that use Semantic UI, whereas Ant Design is used by Telepath, XPrep, and Arhia. Semantic UI has a broader approval, being mentioned in 77 company stacks & 55 developers stacks; compared to Ant Design, which is listed in 24 company stacks and 33 developer stacks.
What is Ant Design?
What is Semantic UI?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Semantic UI?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling
import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle
<head> content, because it works universally, making it easy to throw back the correct
<title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.
<style> tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
Really simple to install and works as you expect it to out of the box.
Ant Design has a lot of different components to choose from, and they looks fantastic. Very enterprise, very polished. This isn't Twitter Bootstrap.
A great thing about a lot of the components is that they take other React components as children. So you can nest, and mish-mash the content to your hearts content.
If you're building something, take a look at Ant Design - it may increase your output speed significantly and make your app not look "MVP".
We use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.
Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.
best practice standardization within the team on a very promising GUI standard design for client development