Why Radix UI Is My Go-To UI Library

Published on May 17, 2024

Over the close to three years that I've been developing apps, I've gotten to work with many different UI libraries. Ionic Framework and Material UI Joy are the two that I used the most before switching to Radix UI. Their easy implementation and appealing UI made them a great starting point, but these two each have their downfalls that made me switch.

Ionic Framework was a great UI to start with. It had easy-to-use components that were also visually appealing and made routing and app logic super easy to manage. The problem with Ionic lies in the above sentence - because it was so easy to implement and use, there weren't many customization options that met my requirements. I needed to be able to customize various configurations for the Ionic components, and Ionic didn't provide the layout components like grids and containers that I needed.

Material UI Joy helped fix a bunch of the issues that I had with Ionic Framework. Not only did it allow for further component customization, but it also provided layout components out of the box. However, Material UI Joy had a little too many configuration options. Many of the configurations still utilize classic CSS style names, which are very unfriendly to developers who are developing large applications.

In contrast, Radix UI has heavily customizable components as well as layout components, and user-friendly style names, and as a bonus, it automatically configures aria accessibility features. I've used Radix UI for a few projects now, including My SchoolDesk and AllKnit, and I'm going to continue to move projects over to Radix UI as I develop incremental builds for my projects.



Mitchell Peck

© 2023 Mitchell Peck. All rights reserved.