Use it on a few websites (<a href="https://www.hskflashcards.com" rel="nofollow">https://www.hskflashcards.com</a>, <a href="https://parataxic.org" rel="nofollow">https://parataxic.org</a>). Like it.<p>- TypeScript<p>- WAI ARIA / a11y for accessibility<p>- Passthrough styling props via Styled System: <a href="https://styled-system.com/" rel="nofollow">https://styled-system.com/</a><p>- Passthrough responsive conditional props: <a href="https://chakra-ui.com/responsive-styles" rel="nofollow">https://chakra-ui.com/responsive-styles</a><p>- Light / Dark: <a href="https://chakra-ui.com/color-mode" rel="nofollow">https://chakra-ui.com/color-mode</a> (but it doesn't work on Gatsby: <a href="https://github.com/chakra-ui/chakra-ui/issues/305" rel="nofollow">https://github.com/chakra-ui/chakra-ui/issues/305</a>)<p>- I eschew some of the helper components like <Flex>. You are fine just using plain old Box as the shorthand props in Flex component don't add much. You can just pass display="flex" into a Box.<p>- Passing hover/active styling requires using PseudoBox (or a component deriving from it), so <Box> - or anything built on top of it - can't have hover colors directly. This means configuration for some components require additional wrappers<p>- Active! <a href="https://github.com/chakra-ui/chakra-ui" rel="nofollow">https://github.com/chakra-ui/chakra-ui</a><p>- Author is very courteous (if my limited interaction with him on the tracker is any indicator!) If you use Chakra and like it, you can support the creator via <a href="https://www.patreon.com/segunadebayo" rel="nofollow">https://www.patreon.com/segunadebayo</a>
I use this library for basically all my projects now, i have tried many component libraries but this is the one I am most productive with<p>The idea of using atomic css properties is similar to the tailwind philosophy but there is no need to purge the css and you get typescript completion and validation
I work with Segun (the creator of Chakra UI), super cool and down to earth dude. I love that Chakra UI is getting some attention. We have been using it in all our production applications and couldn't be happier. I also just finished creating a short project-based video series on Chakra UI and React yesterday. Have a look if anyone is interested <a href="https://www.youtube.com/watch?v=NyG7YJWJd6s&list=PLkZYeFmDuaN3NDLnBG01-sH2-nwn43mYu" rel="nofollow">https://www.youtube.com/watch?v=NyG7YJWJd6s&list=PLkZYeFmDua...</a>
I’m not sure exactly what’s going on, but I noticed in iOS Safari (iPhone 11, iOS 13.5.1), the components get progressively less responsive while browsing the components. After switching to a few component menus, for example, the button presses take ~1s to start animating. Reloading the page appears to reset the responsiveness to normal.
Really happy that Chakra UI is getting some attention here.<p>I interviewed the creator, Segun Adebayo, on the JSParty podcast here: <a href="https://changelog.com/jsparty/125" rel="nofollow">https://changelog.com/jsparty/125</a> You couldn't meet a friendlier maintainer. The fact that he's only been programming full-time for 6-7 months makes Chakra UI even more impressive.<p>I used it to build my recent side project, Virus Cafe (<a href="https://virus.cafe" rel="nofollow">https://virus.cafe</a>) (Show HN: <a href="https://news.ycombinator.com/item?id=23408144" rel="nofollow">https://news.ycombinator.com/item?id=23408144</a>), and it's been an absolute joy to work with.
The component I always look for in these libraries is a date picker (and also a time picker). I've never found one that actually works well on desktop and mobile and can be used with a keyboard.
What is the threshold for UI component libraries describing themselves as "accessible"> Is it running through automated tools, such axe, is it an audit by an independent third-party group, or is it manual testing by actual users who regularly use screen reader tools?
I'd rather just use tailwind or other utility css. Why have another proprietary abstraction when you can have something concise that maps more directly to css. You can then build your own local abstractions as needed. Much leaner, universal and comprehensible imo.
Hello fam! Creator of the Vue version of Chakra UI here!<p>Chimed in a little late, but I'm grateful for the Chakra UI shoutout!<p>The React team is currently working on publishing new 1.0 Typescript release for Chakra UI. Lots of new goodies coming in next major version for React!<p>I've gained some useful insight while reading some of the comments made about the libraries. We'll definitely be looking into this in the near future!<p>The Vue version was recently released a month ago! We're currently improving the release and coming up with new ideas to make developing accessible Vue apps with Chakra UI easier and more fun.<p>If you have any questions about the Vue version (or React) as well, I'm happy to take them!<p>We're also very glad to receive contributors to help us improve Chakra UI. If this sounds like something you're interested in doing, feel free to checkout the issues:<p>Vue repo: <a href="https://github.com/chakra-ui/chakra-ui-vue/issues" rel="nofollow">https://github.com/chakra-ui/chakra-ui-vue/issues</a>
React repo: <a href="https://github.com/chakra-ui/chakra-ui/issues" rel="nofollow">https://github.com/chakra-ui/chakra-ui/issues</a>
I am a big fan of styled-system and glad that more frameworks are utilizing it. This is something that helps a lot when building desktop-alike apps for the web.
I have just launched a cheap fuel finder (for Australia) application using chakra.<p><a href="https://petrolbuddy.net.au" rel="nofollow">https://petrolbuddy.net.au</a><p>It's been such a joy to work with, and I have loved the abstractions so far, especially things like <Flex> and <Box>.
I used to have ant.design as my react frontend first pick.<p>Then I needed to do responsive, and it was much more fun doing this in chakra with it's variable sizes for different viewports, etc, which was much nicer than dabling with ant.design less/css @media queries in my experience.<p>+1 for Chakra-UI
The people who publish this also have a drag and drop interface for assembling low level components into higher level bundles of components, too.<p>Seems to be an all-around well designed system to me, I like it!