Alternatives to UIkIt logo

Alternatives to UIkIt

Bootstrap, Semantic UI, Bulma, Angular Material , and SwiftUI are the most popular alternatives and competitors to UIkIt.
723
326
+ 1
260

What is UIkIt and what are its top alternatives?

UIkit gives you a comprehensive collection of HTML, CSS, and JS components which is simple to use, easy to customize and extendable.
UIkIt is a tool in the Front-End Frameworks category of a tech stack.
UIkIt is an open source tool with 17.1K GitHub stars and 2.3K GitHub forks. Here’s a link to UIkIt's open source repository on GitHub

Top Alternatives to UIkIt

  • Bootstrap

    Bootstrap

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

  • Semantic UI

    Semantic UI

    Semantic empowers designers and developers by creating a shared vocabulary for UI. ...

  • Bulma

    Bulma

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

  • Angular Material

    Angular Material

    Sprint from Zero to App. Hit the ground running with comprehensive, modern UI components that work across the web, mobile and desktop. It allows to create material styled angular apps fast and easy. ...

  • SwiftUI

    SwiftUI

    Provides views, controls, and layout structures for declaring your app's user interface. The framework provides event handlers for delivering taps, gestures, and other types of input to your app. ...

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

  • Cocoa (OS X)

    Cocoa (OS X)

    Much of Cocoa is implemented in Objective-C, an object-oriented language that is compiled to run at incredible speed, yet employs a truly dynamic runtime making it uniquely flexible. Because Objective-C is a superset of C, it is easy to mix C and even C++ into your Cocoa applications. ...

  • React

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

UIkIt alternatives & related posts

Bootstrap logo

Bootstrap

52.7K
11.7K
7.6K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
52.7K
11.7K
+ 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
  • 411
    Open source
  • 375
    Widely used
  • 368
    Customizable
  • 241
    HTML framework
  • 76
    Popular
  • 75
    Easy setup
  • 75
    Mobile first
  • 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
    Easy to setup and learn
  • 4
    Love it
  • 4
    Rapid development
  • 3
    Great and easy to use
  • 2
    Provide angular wrapper
  • 2
    Easy to use
  • 2
    Community
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Popularity
  • 2
    Great customer support
  • 2
    Clean and quick frontend development
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 2
    Great and easy
  • 1
    Material-ui
  • 1
    Reactjs
  • 1
    Geo
  • 1
    Boostrap
  • 1
    Pre-Defined components
  • 1
    Not tied to jQuery
  • 1
    Responsive design
  • 1
    Design Agnostic
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Love the classes?
  • 1
    It's fast
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 1
    Easy setup2
  • 1
    Painless front end development
  • 1
    So clean and simple
  • 1
    Numerous components
  • 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
  • 1
    Super heavy

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 19 upvotes · 2.4M 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 · 760.8K 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
Semantic UI logo

Semantic UI

853
1.4K
672
A UI Component library implemented using a set of specifications designed around natural language
853
1.4K
+ 1
672
PROS OF SEMANTIC UI
  • 157
    Easy to use and looks elegant
  • 92
    Variety of components
  • 64
    Themes
  • 61
    Has out-of-the-box widgets i would actually use
  • 56
    Semantic, duh
  • 44
    Its the future
  • 42
    Open source
  • 37
    Very active development
  • 31
    Far less complicated structure
  • 28
    Gulp
  • 9
    Already has more features than bootstrap
  • 8
    Just compare it to Bootstrap and you'll be hooked
  • 7
    UI components
  • 7
    Clean and consistent markup model
  • 6
    Responsiveness
  • 4
    Elegant. clean. readable. maintainable
  • 4
    Because it is semantic :-D
  • 4
    Good-Looking
  • 2
    Great docs
  • 2
    Consistent
  • 2
    Is big and look really great, nothing like this
  • 2
    Modular and scalable
  • 1
    Jquery
  • 1
    Easy to use
  • 1
    Blends with reactjs
CONS OF SEMANTIC UI
  • 5
    Outdated build tool (gulp 3))
  • 3
    HTML is not semantic (see list component)
  • 2
    Javascript is tied to jquery
  • 2
    Poor accessibility support

related Semantic UI 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
Bulma logo

Bulma

588
695
33
Free, open source, & modern CSS framework based on Flexbox
588
695
+ 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 · 404.5K 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
Angular Material  logo

Angular Material

534
624
26
Easy to use material design for angular
534
624
+ 1
26
PROS OF ANGULAR MATERIAL
  • 10
    Components
  • 6
    Backed by a well known company
  • 3
    Simple
  • 2
    Easy
  • 2
    Very good documentation
  • 2
    Rte
  • 1
    Implements well known material design
CONS OF ANGULAR MATERIAL
  • 3
    Fairly large

related Angular Material posts

SwiftUI logo

SwiftUI

254
262
4
Build user interfaces across all Apple platforms with Swift
254
262
+ 1
4
PROS OF SWIFTUI
  • 2
    Smaller Scalable views
  • 1
    XCode Canvas feature
  • 1
    Live previews
CONS OF SWIFTUI
    Be the first to leave a con

    related SwiftUI posts

    Greetings everyone. I ran a design studio for 8 years in which we designed mobile and web apps. I also lead development teams when our client asked us to carry out the development of the projects. I always had an interest in learning to code to help me understand what is going on on the dev side and also build small apps as a hobby. I tried several times to get on a learning path, but challenges always put me down, so I quit after a couple of weeks. I tried JavaScript, Python, PHP, and Objective-C.

    Now I am retrying to teach myself Swift and especially SwiftUI for more than a month, and It's been going well so far. I want to build my own small apps, and I'm not focused on getting hired as a developer. I want to ask if it's the right language to start learning to program or should I learn something else first as a foundation. I'm currently taking a 100 days of code challenge and reading the Swift 5.3 PDF if I want to get more information on a specific topic. It feels like none of the stuff is sticking, but I'm not sure if it's the way it goes or my approach is wrong.

    I would appreciate any kind of guidance. Thanks

    See more
    Pragna Bhatt
    android and IOS developer at Test · | 3 upvotes · 870 views
    Shared insights
    on
    SwiftUI
    Flutter

    I am new to Flutter... I am not able to make a decision should I use flutter or SwiftUI? application with 8 to 10 modules already done with native code.. now client want other 2 modules so i am confused between flutter and native

    See more
    Foundation logo

    Foundation

    1.2K
    1.1K
    735
    The most advanced responsive front-end framework in the world
    1.2K
    1.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
    Cocoa (OS X) logo

    Cocoa (OS X)

    34
    42
    6
    The Cocoa frameworks consist of libraries, APIs, and runtimes that form the development layer for all of OS...
    34
    42
    + 1
    6
    PROS OF COCOA (OS X)
    • 3
      Great community
    • 2
      IOS
    • 1
      Backed by apple
    CONS OF COCOA (OS X)
      Be the first to leave a con

      related Cocoa (OS X) posts

      React logo

      React

      109.4K
      87.4K
      3.8K
      A JavaScript library for building user interfaces
      109.4K
      87.4K
      + 1
      3.8K
      PROS OF REACT
      • 757
        Components
      • 651
        Virtual dom
      • 562
        Performance
      • 486
        Simplicity
      • 436
        Composable
      • 175
        Data flow
      • 159
        Declarative
      • 124
        Isn't an mvc framework
      • 113
        Reactive updates
      • 111
        Explicit app state
      • 32
        JSX
      • 23
        Learn once, write everywhere
      • 19
        Uni-directional data flow
      • 16
        Easy to Use
      • 14
        Works great with Flux Architecture
      • 10
        Great perfomance
      • 8
        Built by Facebook
      • 7
        Javascript
      • 5
        TypeScript support
      • 5
        Speed
      • 4
        Feels like the 90s
      • 4
        Scalable
      • 4
        Easy to start
      • 4
        Awesome
      • 3
        Fancy third party tools
      • 3
        Hooks
      • 3
        Functional
      • 3
        Server side views
      • 3
        Props
      • 2
        Rich ecosystem
      • 2
        Obama
      • 2
        Very gentle learning curve
      • 2
        Has functional components
      • 2
        Simple
      • 2
        Closer to standard JavaScript and HTML than others
      • 2
        Super easy
      • 2
        Has arrow functions
      • 2
        Strong Community
      • 2
        Great migration pathway for older systems
      • 2
        SSR
      • 2
        Fast evolving
      • 2
        Simple, easy to reason about and makes you productive
      • 2
        Excellent Documentation
      • 2
        Scales super well
      • 2
        Just the View of MVC
      • 2
        Server Side Rendering
      • 2
        Cross-platform
      • 1
        Fragments
      • 1
        Start simple
      • 1
        Every decision architecture wise makes sense
      • 1
        Permissively-licensed
      • 1
        Beautiful and Neat Component Management
      • 1
        Sdfsdfsdf
      • 1
        Allows creating single page applications
      • 1
        Split your UI into components with one true state
      • 1
        Sharable
      CONS OF REACT
      • 35
        Requires discipline to keep architecture organized
      • 23
        No predefined way to structure your app
      • 21
        Need to be familiar with lots of third party packages
      • 8
        JSX
      • 7
        Not enterprise friendly
      • 3
        One-way binding only
      • 2
        State consistency with backend neglected
      • 1
        Bad Documentation

      related React posts

      Vaibhav Taunk
      Team Lead at Technovert · | 31 upvotes · 1.6M views

      I 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.

      See more
      Adebayo Akinlaja
      Engineering Manager at Andela · | 26 upvotes · 718.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—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.

      See more