Alternatives to Semantic UI logo

Alternatives to Semantic UI

Bootstrap, UIkIt, Ant Design, Material-UI, and Material Design are the most popular alternatives and competitors to Semantic UI.
829
1.3K
+ 1
670

What is Semantic UI and what are its top alternatives?

Semantic empowers designers and developers by creating a shared vocabulary for UI.
Semantic UI is a tool in the Front-End Frameworks category of a tech stack.
Semantic UI is an open source tool with 49.3K GitHub stars and 5.1K GitHub forks. Here鈥檚 a link to Semantic UI's open source repository on GitHub

Top Alternatives to Semantic UI

  • Bootstrap

    Bootstrap

    Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...

  • UIkIt

    UIkIt

    UIkit gives you a comprehensive collection of HTML, CSS, and JS components which is simple to use, easy to customize and extendable. ...

  • Ant 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. ...

  • Material-UI

    Material-UI

    It is a comprehensive guide for visual, motion, and interaction design across platforms and devices. ...

  • Material Design

    Material Design

    Material Design is a unified system that combines theory, resources, and tools for crafting digital experiences. ...

  • Bulma

    Bulma

    Bulma is a CSS framework based on Flexbox and built with Sass

  • Semantic UI React

    Semantic UI React

    Semantic UI React is the official React integration for Semantic UI. jQuery Free, Declarative API, Shorthand Props, and more. ...

  • Foundation

    Foundation

    Foundation is the most advanced responsive front-end framework in the world. You can quickly prototype and build sites or apps that work on any kind of device with Foundation, which includes layout constructs (like a fully responsive grid), elements and best practices. ...

Semantic UI alternatives & related posts

Bootstrap logo

Bootstrap

52.2K
11.4K
7.6K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
52.2K
11.4K
+ 1
7.6K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 943
    Consistent
  • 777
    Great docs
  • 677
    Flexible
  • 466
    HTML, CSS, and JS framework
  • 410
    Open source
  • 375
    Widely used
  • 368
    Customizable
  • 241
    HTML framework
  • 76
    Popular
  • 75
    Mobile first
  • 75
    Easy setup
  • 56
    Great grid system
  • 49
    Great community
  • 38
    Future compatibility
  • 34
    Integration
  • 27
    Very powerful foundational front-end framework
  • 24
    Standard
  • 23
    Javascript plugins
  • 19
    Build faster prototypes
  • 18
    Preprocessors
  • 13
    Grids
  • 8
    Clean
  • 7
    Good for a person who hates CSS
  • 4
    Rapid development
  • 4
    Easy to setup and learn
  • 4
    Love it
  • 2
    Clean and quick frontend development
  • 2
    Provide angular wrapper
  • 2
    Great and easy to use
  • 2
    Great and easy
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Community
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 2
    Easy to use
  • 1
    Painless front end development
  • 1
    Responsive design
  • 1
    Reactjs
  • 1
    Geo
  • 1
    Design Agnostic
  • 1
    So clean and simple
  • 1
    Numerous components
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Love the classes?
  • 1
    Material-ui
  • 1
    Pre-Defined components
  • 1
    Boostrap
  • 1
    It's fast
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 1
    Easy setup2
  • 0
    Frefsd
CONS OF BOOTSTRAP
  • 25
    Javascript is tied to jquery
  • 16
    Every site uses the defaults
  • 14
    Too much heavy decoration in default look
  • 14
    Grid system break points aren't ideal
  • 8
    Verbose styles

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Module Lead | 18 upvotes 路 2.3M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Francisco Quintero
Tech Lead at Dev As Pros | 13 upvotes 路 694.7K views

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
UIkIt logo

UIkIt

717
310
260
A lightweight and modular front-end framework for developing fast and powerful web interfaces
717
310
+ 1
260
PROS OF UIKIT
  • 37
    Complete GUI
  • 29
    Easy modify
  • 27
    Practical
  • 24
    Easy to learn
  • 24
    Functional
  • 22
    Intuitive
  • 21
    Free
  • 16
    Simple
  • 15
    Lightweight
  • 15
    Easy to use
  • 5
    Modern look
  • 5
    Because I can create amazing things with little effort
  • 5
    Modular
  • 4
    Responsiveness
  • 3
    Small but Active Community
  • 2
    Responsive grid
  • 2
    No requires jquery
  • 2
    Convenient JS Components
  • 2
    Based on Flexbox
CONS OF UIKIT
    Be the first to leave a con

    related UIkIt posts

    Daniel Hern谩ndez Alcojor
    Frontend Developer at atSistemas | 8 upvotes 路 301.3K views

    I'm building, from scratch, a webapp. It's going to be a dashboard to check on our apps in New Relic and update the Apdex from the webapp. I have just chosen Next.js as our framework because we use React already, and after going through the tutorial, I just loved the latest changes they have implemented.

    But we have to decide on a CSS framework for the UI. I'm partial to Bulma because I love that it's all about CSS (and you can use SCSS from the start), that it's rather lightweight and that it doesn't come with JavaScript clutter. One of the things I hate about Bootstrap is that you depend on jQuery to use the JavaScript part. My boss loves UIkIt, but when I've used it in the past, I didn't like it.

    What do you think we should use? Maybe you have another suggestion?

    See more
    Ant Design logo

    Ant Design

    679
    1.1K
    190
    A set of high-quality React components
    679
    1.1K
    + 1
    190
    PROS OF ANT DESIGN
    • 36
      Lots of components
    • 27
      Polished and enterprisey look and feel
    • 18
      TypeScript
    • 17
      Easy to integrate
    • 17
      Es6 support
    • 15
      Beautiful and solid
    • 14
      Beautifully Animated Components
    • 13
      Quick Release rhythm
    • 12
      Great documentation
    • 12
      Typescript support
    • 9
      Short Code
    CONS OF ANT DESIGN
    • 14
      Less
    • 7
      Large File Size
    • 6
      Close
    • 2
      Poor accessibility support
    • 1
      Sdf

    related Ant Design posts

    Sarmad Chaudhary
    Founder & CEO at Ebiz Ltd. | 9 upvotes 路 362.6K views

    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 :)

    See more
    Shared insights
    on
    Material-UI
    Ant Design

    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.

    1. Good documentation.
    2. easy CRUD ( date picker and date range picker bundled )
    3. built-in multi-lang feature or Great 3rd library support
    4. Admin dashboard template
    5. well code maintenance

    Which is better for the long run?

    See more
    Material-UI logo

    Material-UI

    1.3K
    2.5K
    338
    React components for faster and easier web development
    1.3K
    2.5K
    + 1
    338
    PROS OF MATERIAL-UI
    • 107
      React
    • 70
      Material Design
    • 45
      Ui components
    • 23
      CSS framework
    • 17
      Component
    • 10
      Looks great
    • 9
      Responsive
    • 9
      LESS
    • 6
      Open source
    • 6
      Good documentation
    • 5
      Code examples
    • 5
      Flexible
    • 5
      Ui component
    • 4
      JSS
    • 3
      Angular
    • 3
      Very accessible
    • 2
      Fun
    • 2
      Designed for Server Side Rendering
    • 2
      Supports old browsers out of the box
    • 2
      LADO
    • 1
      Interface
    • 1
      Asdasd
    • 1
      Easy to work with
    • 0
      555
    CONS OF MATERIAL-UI
    • 24
      Hard to learn. Bad documentation
    • 21
      Hard to customize
    • 16
      Hard to understand Docs
    • 6
      Bad performance
    • 5
      Long Code
    • 4
      Extra library needed for date/time pickers
    • 4
      For editable table component need to use material-table

    related Material-UI posts

    Adebayo Akinlaja
    Engineering Manager at Andela | 22 upvotes 路 627.1K views

    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鈥攕ince 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.

    See more

    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?

    See more
    Material Design logo

    Material Design

    492
    672
    11
    Google's Material Design
    492
    672
    + 1
    11
    PROS OF MATERIAL DESIGN
    • 4
      They really set a new bar in design
    • 3
      An intuitive design
    • 2
      Simply, And Beautiful
    • 2
      Many great libraries
    • 0
      Composants
    CONS OF MATERIAL DESIGN
    • 1
      Sometimes, it can hang the browser

    related Material Design posts

    Giordanna De Gregoriis
    Jr Fullstack Developer at Stefanini Inspiring | 7 upvotes 路 8.3K views

    TL;DR: Shall I keep developing with Nuxt.js 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

    Long version: We have an old web application running on AngularJS and Bootstrap for frontend. It is mostly a user interface to easily read and post data to our engine.

    We want to redo this web application. Started from scratch using the newest version of Angular 2+ and Material Design for frontend. We haven't even finished rewriting half of the application and it is becoming dreadful to work on.

    • The cold start takes too much time
    • Every little change reload the whole page. Seconds to minutes of development lost looking at a loading blank page just changing css
    • Code maintainability is getting worse... again... as the application grows, since we must create everytime 5 files for a new page (html, component.ts, module.ts, scss, routing.ts)

    I'm currently trying to code a Proof of Concept using Nuxt.js and Tailwind CSS. But the thing is, Vue.js 3 is out and has interesting features such as the composition API, teleport and fragments. Also we wish to use the Vite frontend tooling, to improve our time developing regardless of our application size. It feels like a better alternative to Webpack, which is what Nuxt 2 uses.

    I'm already trying Nuxt.js with the nuxt-vite experimental module, but many nuxt modules are still incompatible from the time I'm posting this. It is also becoming cumbersome not being able to use teleport or fragments, but that can be circumvented with good components.

    What I'm asking is, what should be the wisest decision: keep developing with Nuxt 2 and wait for a migration guide to Nuxt 3? Or start developing with Vue.js 3 using Vite, and then migrate to Nuxt 3 when it comes out?

    See more
    Ashish Sharma
    Sr. UI Associate at Daffodil Software | 4 upvotes 路 246.3K views

    I am a bit confused when to choose Bootstrap vs Material Design or Tailwind CSS, and why? I mean, in which kind of projects we can work with bootstrap/Material/Tailwind CSS? If the design is made up on the grid, we prefer bootstrap, and if flat design, then material design. Similarly, when do we choose tailwind CSS?

    Any suggestion would be appreciated?

    See more
    Bulma logo

    Bulma

    536
    648
    33
    Free, open source, & modern CSS framework based on Flexbox
    536
    648
    + 1
    33
    PROS OF BULMA
    • 10
      Easy setup
    • 6
      Easy-to-customize the sass build
    • 6
      Community-created themes
    • 4
      Great docs
    • 4
      Responsive
    • 3
      Easy to learn and use
    CONS OF BULMA
    • 2
      Not yet supporting Vue 3

    related Bulma posts

    Daniel Hern谩ndez Alcojor
    Frontend Developer at atSistemas | 8 upvotes 路 301.3K views

    I'm building, from scratch, a webapp. It's going to be a dashboard to check on our apps in New Relic and update the Apdex from the webapp. I have just chosen Next.js as our framework because we use React already, and after going through the tutorial, I just loved the latest changes they have implemented.

    But we have to decide on a CSS framework for the UI. I'm partial to Bulma because I love that it's all about CSS (and you can use SCSS from the start), that it's rather lightweight and that it doesn't come with JavaScript clutter. One of the things I hate about Bootstrap is that you depend on jQuery to use the JavaScript part. My boss loves UIkIt, but when I've used it in the past, I didn't like it.

    What do you think we should use? Maybe you have another suggestion?

    See more
    Semantic UI React logo

    Semantic UI React

    204
    296
    25
    Integrating Semantic-UI and React
    204
    296
    + 1
    25
    PROS OF SEMANTIC UI REACT
    • 9
      Great look&feel
    • 5
      Really adaptive -good support of different screen sizes
    • 5
      Great lib, lots of components enough to build a big app
    • 3
      Extensible and lots of components but no transitions
    • 1
      Easy Customization
    • 1
      JSS
    • 1
      Documentation is also understandable
    CONS OF SEMANTIC UI REACT
    • 3
      Poor Documentation
    • 1
      Sdf

    related Semantic UI React posts

    Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

    We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

    See more

    We chose to use React as our frontend. This will allow us to effectively manage and condense our code into repeatable components to avoid repetition and promote clarity. We have also decide to use Redux as it has proven to be an efficient way to manage a state space given a complex and scalable product such as ours. To avoid costly time and effort with boiler plate styling of common components, we have decided to use the Semantic UI React open-source library as it provides great customization and clear documentation. Lastly, we will be using Jest for frontend Unit testing, as it is a popular framework and has great support for React.

    See more
    Foundation logo

    Foundation

    1.2K
    1K
    735
    The most advanced responsive front-end framework in the world
    1.2K
    1K
    + 1
    735
    PROS OF FOUNDATION
    • 158
      Responsive grid
    • 92
      Mobile first
    • 79
      Open source
    • 75
      Semantic
    • 72
      Customizable
    • 51
      Quick to prototype
    • 50
      Simple ui
    • 45
      Fast
    • 44
      Best practices
    • 39
      Easy setup
    • 6
      Neutral style
    • 6
      HTML, SCSS and JS
    • 5
      Professional
    • 5
      Accessibility support
    • 3
      Xy grid
    • 2
      Every new version is smaller, smarter & more efficient
    • 2
      Sass
    • 1
      Robust
    CONS OF FOUNDATION
    • 4
      Awful site
    • 4
      Requires jQuery

    related Foundation posts

    ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

    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.

    styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <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.

    See more
    Shared insights
    on
    Bootstrap
    Foundation

    Should I go with Foundation CSS instead of Bootstrap? Or, if any other popular responsive frameworks are out there, please suggest them to me. My site mainly targets mobile or tablet

    See more