Chakra-ui Alternatives

chakra-ui reviews and mentions

• An Overview of 25+ UI Component Libraries in 2023
  40 projects | dev.to | 10 Sep 2023

  ChakraUI: An emphasis on A11y, meaning it is fully compatible with the WAI-ARIA accessibility standard, has won OSS awards, and has a thriving community. As mentioned, it’s one of the better choices out there as it has a great model for building composable UI, built-in hooks, and great dark-mode support. This is the same team behind Zag.js, which handles UI as state machines. Once again, you’d need to learn the API, and swapping might be hard to do.

• 🚀 Dominate React Project Startups: Insider Tips for Dev Success! 🤓
  9 projects | dev.to | 26 Aug 2023

  Chakra UI 🌈

• Chakra UI vs Shadcn UI
  7 projects | dev.to | 16 Aug 2023

  In this article, we shall discuss about Chakra UI and Shadcn UI. Also, their differences, similarities and which to choose when building your project.

• 10 Best Free React UI Libraries in 2023
  21 projects | dev.to | 31 Jul 2023

  As of August 2023, it has got 30K+ GitHub stars and 450K+ weekly downloads on NPM.

  21 projects | dev.to | 31 Jul 2023

  Chakra UI is another popular UI component library often used by React developers to design components. Similar to the previous two libraries, it is also an open-source project.

• React-ing to accessibility: Building accessible e-commerce forms that everyone can use
  4 projects | dev.to | 20 Jul 2023

  If you want to take a look at other component libraries, I invite you to read a little more about Chakra UI, which is a modular and accessible library which I personally really enjoyed working with. I also had the chance to read about React Aria, which is an accessible-focused package for React, developed by Adobe; however, this library has a great difference: instead of focusing on components, it uses a hooks-based API.

• Tailwind Component Library - Which one do you use?
  5 projects | /r/tailwindcss | 9 Jul 2023

  Loving https://chakra-ui.com/ and https://chakra-templates.dev/

• On the search for a truly "good" UI framework.
  10 projects | /r/webdev | 2 Jul 2023

  The next thing I found was ChakraUI, and I even started building with it. The lack of a Layout component, and some other issues with the docs and it being a comparatively small project with slow support and the discord not being too active was not what really turned me off. ChakraUI looks decent, but it's too unopinionated for my liking. I want to ship, not have to configure Buttons with 16 lines of props first.

• Ask HN: How can a BE/infra developer handle the FE side of personal projects?
  7 projects | news.ycombinator.com | 13 Jun 2023

  - Vercel for hosting, because they take a Git repo and host it for you in a couple clicks and manage everything. Free or cheap ($20/mo) at MVP stage.

  - Next.js (Vercel's open-source React framework) will handle frontend tooling, routing, type checking, and linting for you with a single command (`npx create-next-app`). Starting the server is one more command (`next dev`) and your page is up and running.

  - For the UI layer, I'd recommend either starting with one of their prebuilt templates (https://vercel.com/templates/next.js) and modifying it as needed

  OR using a modern component system like https://mui.com/ or https://ant.design/ or https://chakra-ui.com/ instead of trying to learn and write your own component and JS+CSS code. Using one of these systems will allow you to compose complex apps out of well-made, well-documented, easy-to-use primitives, making it much easier to focus on business needs rather than basic frontend components and infra.

  The basic MUI system, for example, is totally free. You can find third-party apps built on top of it (https://mui.com/store/#populars) and pay a one-time license fee to essentially "fork" them, getting a prebuilt working app that you just attach your backend API calls to.

  There are also low-code extensions of these frameworks (meaning you start with a GUI, plan out your app that way, but still have access to the source for future advanced changes). Examples are https://mui.com/toolpad/ and https://retool.com/use-case/dashboards-and-reporting

  ----------------------

  Is this a lot? Yes and no. React has a learning curve of its own, but it can take the place of having to learn raw HTML and CSS. (Yes, you eventually should know those things for debugging and polishing, but they are largely a level of abstraction below what you really need for a basic MVP).

  Once you learn React, its primary value isn't that it's a great language (opinions differ) but that it has a humongous ecosystem of third-party vendors, free open-source libraries (basically any component you might think to build is probably already available on npm), and a wide availability of devs from hobbyists to full-timers.

  Others in this topic will suggest going away from Javascript as much as possible (and using things like HTMX or backend-to-HTML solutions like the old days). That's fine, but you lose out on the rich ecosystem of React and Javascript, so you end up having to build more yourself -- which is what you're trying to avoid in your case.

  My own 2¢: As someone who grew up with HTML and made websites since the birth of Javascript and CSS, the web has always been messy. It's always been a semi-open ecosystem controlled by a few major companies (whether that's Netscape or Microsoft or Sun or Adobe, or these days Google and Apple), so it very much suffers from design-by-bullying. Whoever is the power player of the decade gets to add their favorite technologies that everyone else is forced to adopt. Thus the web became a hodgepodge of document markup systems poorly fitted for modern apps, with various hacks on top of hacks built to satisfy some big company or another's in-house needs. Sadly, that means going "vanilla HTML+JS" doesn't leave you with much, just the shattered legacy of poor historical decisions.

  React at least helps by encouraging componentization and abstraction of UI elements to functions, using cleaner data models (actual variables and objects) vs direct DOM manipulation (storing page content as state).

  We've gone through many generational shifts in approach, from the raw HTML days of Geocities to the you-build-it, we-host-it approach of Godaddy and its ilk, to the "all in one" CMSes like Wordpress or Drupal. These days, (if you want there to be), there can be a pretty clear separation between backend and frontend systems, and with that specialization came a bunch of startups (mentioned above) whose approach is "let us help you build it as best as we can, so you can focus on business logic instead of basic UI and infra". After 20 years of doing this, the current state of the web developer experience is actually my favorite so far. HTML and CSS suck for building apps (as opposed to documents), and although Javascript is a lot better since ECMAscript v6 (ES6), it is still inextricably tied to the DOM (and thus HTML elements) unless you use an abstraction like React.

  It's the difference between writing something like:

  ```

• How to Create a Code Editor in React and ChakraUI
  2 projects | dev.to | 2 Jun 2023

  By leveraging Chakra UI, we gain access to a wide range of pre-built components that facilitate the creation of a visually appealing and user-friendly interface.

• A note from our sponsor - Amplication
  amplication.com | 22 Sep 2023

  An open-source platform that helps developers build backends without spending time on boilerplate & repetitive coding. Including production-ready GraphQL & REST APIs, DB schema, DTOs, filtering, pagination, RBAC, & more. Learn more →