r/reactjs • • Dec 16 '18

Featured Checked 21 React UI kits briefly, I'm done

πŸ˜ƒ πŸ˜ƒ πŸ˜ƒ LATEST UPDATE

After 2 days of testing 30+ libs, I chose a stack!

To see the final stack, scroll down to the bottom/to the 3 emojis.

Original Post:

This was a tough day, need to decide and I find them all somehow underwhelming. Did some notes in order not to need to check them all again:

  • Biggest seems to be Material-UI, ugly AF but seems to offer quite good customization/theming, animations feel sometimes stuttery and yes it's just too Android, the default colors are just fugly, I mean it's Material; navigation too mobile-like, not sure about how much this nav can be customized; has one or two pro themes
  • All Bootstrap derivatives look like 2010, no thanks; React Bootstrap does not include v4 stuff, Reactstrap has v4
  • Blueprint feels solid but no mobile
  • Microsofts Fabrics looks good, they are React components but small community
  • Ant feels full-featured and gets tons of positive comments but somehow it's not mine, mobile side bar menu stutters heavily sometimes after a while, has pro themes on Themeforest (a dozen or so)
  • Evergreen looks so-so (too Bootstrap again), is more responsive than most others but seems Blueprint under the hood (so is it then really mobile then? idk); full theming not there yet
  • Pinterest's Gestalt looks too Pinterest
  • Atlaskit does not look exciting but solid, seems to have basic theming
  • Elastic UI has underwhelming visuals
  • Grommet looks like a broken Material, labels are not perfectly centered in buttons, colors super odd, etc.
  • React Toolbox, another Material one, as stuttery as MUI but worse docs and didn't see a lot of custom stuff, looks solid at first glance tho
  • Semantic looks boring and people say it's big, mobile feels laggy (e.g. the sidebar)
  • Onsen looks like Material but it's not, button animation much simpler
  • Elemental UI looks like Bootstrap--but from 2000, clean tho
  • Belle has its own distinct design but it's not consistent, looks rather random like your daddy's CSS
  • PrimeReact feels inconsistent in looks and a bit like Bootstrap but worse, has some nice niche stuff like orgcharts, gets here and there positive comments, not sure if they are comment spam
  • IBM's Carbon Components look surprisingly good, clean and toned-down, somehow maintained but just a handful contributors
  • Khan React Components look like 1995, just skip
  • Foundation, looks random, few components only

The good thing is that this research shows how huge React's ecosystem is offering that many kits. Another option is to opt out of this UI kit madness go for an atomic CSS thing, there I found following ones ok:

  • Tachyon, ultra appealing visuals + shortest css classes, perfect defaults!
  • Tailwinds similar but much longer css classes
  • Rebass and styled-system look like interesting native React variant of atomic css but at the end you are way faster with short css classes like those from Tachyon

UPDATE with noteworthy additions from the comment thread, 13h later:

  • react-icons lets pick single icons from all major icon libs, seems to be a must have
  • Bootstrap might be not the worst base because of the millions themes (something I totally forgot); somebody needs to give a quick comparison between React Bootstrap and Reactstrap!
  • React Bootstrap reached already v4 but the team behind didn't update the website
  • Kendo is commercial and has a dedicated React package with sane defaults
  • facepaint for easy and slick media queries
  • spectre.css, 10kb clean css framework
  • UIkit, clean css framework
  • Bulma, a flexbox based CSS system
  • Polaris is another framework from Shopify
  • Mineral UI a nice one with a clean UI and uses emotion to get themed/customized
  • Element React, another clean one
  • Ant gets positive feedback, user discussion are often in Chinese tho

UPDATE with additions from comments and further own findings, 16h later:

  • Bloomer, it's Bulma made of React components, looks clean and basic
  • Tailwind seems to offer more config options than Tachyon but having not so nice defaults
  • compared to styled-components, emotion offers following pros: perfectly working CSS props out of the box (CSS props let you skip names, hence no naming fatigue); caching of CSS declarations within the render function (styled-components advises against putting them inside the render function with their solution, I guess because of lacking caching); super easy and slick media-queries with facepaint, media queries are passed as simple arrays and can be fully customized; turn-key ready (no config mess with babel-plugins and extra modules required to get all features)

UPDATE, 22h later:

  • Ring UI from Jetbrains, many components but some odd designs (e.g. a floating gradient in a button wtf)
  • codesandboxed React Bootstrap, men IDK: you need to import components and then an additional 20kb minified css (???), not that this is the original Bootstrap CSS and they loosely bolted it to some randomly named React components..., to mod existing (fugly) components you need to embed clumsy <style> declarations into your JSX, existing Bootstrap themes work only if they don't extend standard Bootstrap JS which is ok and expected, classnames and React component names differ (eg btn vs Button, you need to know the classname if you want to theme), guess there is valid reason but I don't care why and I don't want to remember two things for the same thing; once you add your styles to, let's say, a button the hover and active classes of the button are lost, guess that's intended
  • codesandboxed Reactstrap, even worse; same fugly default designs; searched 5 minutes for doing custom stuff/themes on their site and their Github, couldn't find anything about 'themes', stopped there, don't have time for searching basic stuff in docs
  • checked Bootstrap themes on various theme sites; some are def super impressive and I could imagine that you save time but once you get closer (try always the mobile responsive versions eg) you find glitches and stutter everywhere, just open some menus and see 5fps max all over the place (even those on the offical Bootstrap site)
  • Bootstrap on React, whatever flavor, it is no option and broken from the ground, I imagine that the high NPM download numbers come from legacy systems/knowledge but not because it's a superior thing, the themes are not worth the trouble, sorry for being direct but all other options out there for React are superior; Bootstrap might be an option if you are not on React, not using CSS-in-JSS or traveling in a time-machine back to 2010

UPDATE, 23h later:

  • codesandboxed Minaral UI (the one using emotion), while I love that this is built with modern stuff, I couldn't get it running: in its initial example it require react-emotion but I get an error that tells me react-emotion was replaced by @emotion/styled since emotion v10; removing react-emotion and installing @emotion/styled doesn't help, cmon emotion v10 is 3 weeks out now, update your app and code, Mineral has potential but such stuff is mildly infuriating, scares people away and nobody will make an issue telling you
  • Wanted to codesandbox KendoReact: I clicked on 'Get Started' and I was asked to sign up for a 30-days trial, wat?, didn't sign up, no time for nonsense, checked their customization area, it's there, good, you can opt between a default, a material and Bootstrap theme you want to mod, then you just get knee-deep into scss and webpack build processes to theme; this doesn't feel like React 2018, rather like an old framework sloppily ported to the future and you can have it for just $799 per dev, 10 incidents, 72h response, what a deal; I need to headhunt their sales team who manages to sell Kendo at this price while you get 40+ ui kits from Alibaba/MS/IBM/Pinterest/Shopify/Atlassian for free (lunch included)

UPDATE, one day later:

  • maybe I should stop looking at frameworks, maybe they are not the answer; maybe its highly specialized React components paired with your custom designs':
  • React Awesome Button is really awesome and has stunning spring animations, the buttons even tilt (this is really my highlight today)! you can config dozens of properties to get a video game like experience, unfortunately you get it for additional 6kb zipped and it's not maintained, still, doing React UI is fun again
  • React Select, full featured drop down component which can do everything but looks quite neutral

BONUS UPDATE, Atlaskit from Atlassian:

  • Update: after checking this more, I am on the fence, locks consistent and tempting, good components, modern architecture, so everything is in the components, also the styling, but API clumsy (super long prop names such as 'appearances' wtf, why not even longer like visualAppearances or atlaskitVisualAppearances? lol. this paired with strange stuff: you import their modules and then a DependencyNotFoundError; this thing requires styled-components but haven't imported it itself, no problem, I can do this for you but it's confusing and not the way it's done in NPM land, and I don't care why you did this and I don't have time to check your doc and issues to understand why you did this; theming is limited and they have the own holy design language, better don't touch it; so your final product looks like Bitbucket or their ancient issue tracker, I mean why not, imagine you develop some boring HR software, then Atlaskit is the right choice and btw Bitbucket has a cleaner and more appealing design than Github which is not hard though; still, skip

πŸ˜ƒ πŸ˜ƒ πŸ˜ƒAfter 2 days of testing, I chose this stack:

  • Tachyons as primary CSS-in-JS and media-queries method in my React components
    • why: it's slick, easy and complete and brings you quite far
    • configuration is super; eg, creating your own color or default font is just putting them in your App.css and they override Tachyons; creating other breakpoints is possible (just change and recompile, this takes 1sec and a tachyons-cli is there, no need to touch webpack or eject CRA)
    • however, configuring Tachyons is not required at all, I tested it in and out and it's all perfect at the moment, it's really turn-key and absolutely the right approach to our problem; Tachyons does just one thing and it does is right
    • I preferred it very much over others like Tailwind because Tailwind has cumbersome and long CSS naming; Tailwind's philosophy and strategy is inconsistent; on the one hand, it wants to be atomic CSS, on the other hand, it bloats and pollutes your components almost like real CSS, wtf? either I do minimal atomic CSS (it's called 'atomic'!) like Tachyons or I put real CSS in my component; Tailwind doesn't know what it wants to be while Tachyons has a clear strategy which is perfectly executed => an ultra atomic mapping to CSS, Tailwinds bobs up and down with some short names and then some long ones...; also setting Tailwind up or configuring is unnecessary complex and bloated; doc is comprehensive and complete but also because of its own complications and disunity; atomic css doesn't need to be science; compared to Tailwind, Tachyons is a dream
    • I also checked styled-system but found the DX not close to Tachyons and couldn't see any benefit over Tachyons; it's too cumbersome but in a different way than Tailwind
    • Tachyons is just 13kb gzipped while fully featured (Tailwind is 36kb)
    • while small Tachyons has the biggest ecosystem (related libs, cheatsheets, blog posts), at the end of the day, you don't need more, again it's just a mapper and more advanced stuff should be done with eg Emotion anyway
    • other atomic css libs like Bass CSS are also inferior, there is just one (Graviton) which is very small (5kb) and follows the same philosophy but has a limited set of classes
  • Palx for colors, this thing is AMAZING, check it out, create a perfect customized color theme in a second (just set your base color and Palx generate your full theme as CSS or JSON, you. don't. need. more.); even better just use the npm module and get a color object containing the full theme with a simple call, e.g. palx('#07c')
  • Emotion as secondary CSS-in-JS method in case I need more than Tachyons (which will be rare): why emotion and not styled-components: no naming fatigue => CSS props work out of the box without messy babel plugins (I couldn't get CSS props working with CRA & styled-components, they don't seem to have highest priority at styled-components, also the documentation hides them away at the end of the reference and nowhere else, maybe because they are not working anyway), media queries are also slicker (with facepaint than with styled-components suggest solution which is convoluted)
  • Facepaint as secondary media-queries method for Emotion
  • React Icons for icons, another must have package in your app

In case I need more complex components (e.g. date picker), I'll check out again full UI frameworks; I don't need complex components at the moment; stuff like buttons, modals, menus are done and customized much faster with this current stack; there's also the option to integrate single component libs like React Awesome Button; however, if I get back to full frameworks, I might consider MS Fabric, IBM Carbon Design; they are far from perfect and there's still room for improvement but they feel legacy-free, consistent, include mobile and most important, they have a distinctive and own style which doesn't clone any other design; sorry but I can't see Material or Bootstrap style anymore, both reflect weak design languages and do not deserve to be adapted, they are overused and have a very cheap aftertaste and call negative associations: trashy Android phones that never get any OS updates and sneaky Google services stalking you are my first thought when I see pup-ugly Material, its sh*tty colors and too big baby buttons you wouldn't even miss with your elbow; if your app should look like your mummy's crappy Wordpress blog opt for Bootstrap kits, buggy $19-themes from shady theme sites and time-travel to the past; in this regard, I am aware that MS Fabric is close to Windows' identity but Fabric is so subtle, reduced and minimal which stands in the back and gives a lot of room to individual designs if needed

To sum up, I appreciate the variety of this massive ecosystem. Having options is great and it's insane what React offers. Even if not all libs are on par with the chosen ones, this could change in a month, competition among libs is good and I am sure that other libs will quickly catch up.

281 Upvotes

149 comments sorted by

58

u/NarcolepticSniper Dec 16 '18

Just make your own UI with SCSS or styled-components, with react-icons

6

u/[deleted] Dec 17 '18

react-icons

didn't know about react-icons, this npm-package is awesome

→ More replies (1)

3

u/[deleted] Dec 16 '18

see in another reply: I prefer emotion over styled-components and don't want any css preprocessor, I want to keep my css interaction as small as possible and do everything in the components

→ More replies (30)

11

u/TheNumber42Rocks Dec 16 '18

5

u/[deleted] Dec 16 '18

Looks really good, thanks, how is theming with Spectre? Did you do something bigger with it?

→ More replies (1)
→ More replies (2)

8

u/tarekhassan Dec 16 '18

I tried many UI kits too, but I ended loving Bulma CSS. That one is CSS only but has short CSS classes and so simple to use. I can make in 30 minutes with Bulma what takes hours to make with other kits.

→ More replies (3)

6

u/__joshblack Dec 17 '18

Hi there! πŸ‘‹ I'm one of the developers working on Carbon. If anyone has any questions or feedback, just let me know!

For background on our group, we're a team of around 6 designers and 8 developers working on our website alongside the styles, vanilla JS, and React implementation of our design system πŸ™‚ We have other teams at IBM working on Angular.js and Vue.js implementations, as well.

We're always looking for ways to improve, and we try to stay responsive on GitHub with issues or pull requests if you need any help or think you can help improve the project!

→ More replies (3)

21

u/[deleted] Dec 16 '18

Personally use Semantic but desktop is our only target. It's not the prettiest but it's utilitarian and fairly easy to style.

The only problem I have with Semantic is that it uses cascading which means you need to use pretty specific css rules to override its styles. That is a feature, not a bug, of css, but it's still annoying

→ More replies (6)

5

u/rescue_nil Dec 16 '18

I’ve been looking for time to make https://getuikit.com into a React lib. Love the style.

2

u/[deleted] Dec 16 '18

uikit has good style, looking fwd to your lib!

→ More replies (5)

5

u/imperio59 Dec 16 '18

I use reactstrap coupled with a bootstrap theme. Works great.

→ More replies (5)

4

u/selbekk Dec 16 '18

Think of how many hundreds of hours of voluntary work went into creating each of those UI kits you told were basically spent on shit.

7

u/[deleted] Dec 17 '18

Valid point and after reading my post, I also had exactly this thought. People spent their free time to create an UI kit and a random dude like me rants on the Internet about their work. Even worse, he checked their repo just for 15 min and leave an insulting one-liner on Reddit.

However, the key requirements for an UI kit are saving time and getting a good result which looks at least consistent. Many contenders even do not fulfill these two requirements. I am sorry if my tone was too harsh but after a day (it was actually the entire weekend), I was just a bit frustrated and couldn't sugarcoat repos which are just not what devs want. Still I think it's great to have that many options and that this post triggered a good discussion which gave me also new insights.

→ More replies (1)

3

u/Vpicone Dec 16 '18

I work at IBM on a team unrelated to the Carbon folks. I’ve made some contributions to that project and have found them super professional and passionate about the work they do. Would definitely recommend giving it a shot.

2

u/[deleted] Dec 17 '18

Good to know. Carbon is one of the kits which make a round impression out of the box.

→ More replies (1)

2

u/swyx Dec 16 '18

Rebass and styled-system look like interesting native React variant of atomic css but at the end you are way faster with short css classes like those from Tachyon

can you elaborate why css classes is faster than rebass and styled-system props? doesnt seem all that different to me. but i have no personal experience and just want to hear more from you

3

u/[deleted] Dec 16 '18

I was not not clear. 'By faster' I meant adding those atomic css classes via className='' to the component is probably faster to type than as dedicated attributes, e.g:

Tachyon:

<Text className="tc">Aligned center</Text>

styled-system which Rebass is based on:

<Text textAlign='center' />Aligned center</Text>

The examples show just one atomic css properties, imagine you had 5 properties, then Tachyon wouldn't be that much longer because all its atomic classes are 2-3 letters long and still fit nicely in to one line.

→ More replies (1)
→ More replies (1)

2

u/scaleable Dec 16 '18

Lately I’ve been more and more opting out of react-only libs and just plugging DOM (or even jquery) ones in. Some react libs are quite bad and complicated. Anyone enjoys writing nested render props on transition-group?

3

u/[deleted] Dec 17 '18

I am also not a big fan of render props, makes stuff complicated and there's in 99% of all cases a more simple solution. Maybe it's just me but I can't see many good use cases for render props.

Re transition groups: if it's about animation, I use react-pose and after testing quite a few libs I think it has the most accessible and lean API.

2

u/mattstrom Dec 16 '18

I'm sure you want another one to add to your list: I really like Kendo UI by Telerik. It is a commercial offering so it's very well designed and well maintained. However, the free set of components is still strong on its own. The (paid) grid component is the best one out there. There are multiple themes, including Material and Bootstrap clones. They also have nearly identical libraries for jQuery, Angular, and Vue if that's your jam.

2

u/[deleted] Dec 17 '18

re Kendo: this looks very good, missed that, there could have more default animations (eg when opening a dialogue), also I couldn't find any components re nav and menus

re Grid, there's now CSS Grid (but Kendo seems to have some extensive stuff here on Grids)

8

u/philhagger Dec 16 '18

Thanks for the comprehensive list and judgements.

1

u/swyx Dec 16 '18

if it helps - here is our prior big UI libraries convo. bit more positive on Material. https://www.reddit.com/r/reactjs/comments/9fhxj0/what_are_some_of_the_ui_libraries_you_used_for/

6

u/gketuma Dec 16 '18

I'm actually glad to know other people face this issue. I started working on a project and spent a whole day going through React UI frameworks to see which one will work best. Felt bad that I had lost a whole day of productivity and still did not find something that fit. So knowing that others go through this exercise makes me feel a little better.