Skip to main content

Using shadcn ui with adobe's react aria

··747 words·4 mins
Shadcn React-Aria Radix-Ui
Table of Contents

TLDR; use jolly-ui with shadcn to get shadcn styles with react aria components

In this article we will explore shadcn ui library, its unique approach to components, drawbacks to its current approach and how to fix them by using react aria library in conjunction with it.

Shadcn UI library

Shadcn is a UI component library designed to help developers create websites quickly with special emphasis on accessibility. It provides a collection of pre-styled components that can be easily integrated into your projects.

It takes a bit different approach from other UI libraries in the sense that components are added to your code instead of acting as dependency. If you look at your 'package.json' you will not find any dependency added to it when you install shadcn. You can directly copy/paste components from shadcn or you can use cli that automates this process for you, either way components become part of your code. This approach provides maximum customization and independence from updates, ensuring your design remains consistent.

So what's the rationale behind this choice? Well, for one, it avoids any downstream issues that can crop up when a UI library updates with breaking changes. Your copies of the component code are essentially frozen at the version you copied. You don't have to worry about an update causing issues or refactoring your code.

Additionally, this model gives you flexibility. You can easily tweak the components' markup, logic, and styles to suit your unique needs without running into overriding issues. The code is yours to mold. This has a bit of downside as well, since your changes diverge with shadcn and updates to shadcn needs to be merged manually.

Underneath Shadcn, Radix UI powers the interactive components. Radix UI is a low-level component library that focuses on accessibility and customization. It provides unstyled components that can be styled according to your needs. Shadcn adds its own styles on top of it and gets accessibility for free. Some shadcn components use other libraries as well but most of the components rely on radix-ui

Radix-UI has some drawbacks too which because of dependency become drawbacks of shadcn

  • Unintutive code style

    Take a look at example below

        <ContextMenuTrigger>Right click</ContextMenuTrigger>
          <DialogTrigger asChild>
          <DialogTitle>Are you absolutely sure?</DialogTitle>
            This action cannot be undone. Are you sure you want to permanently
            delete this file from our servers?
          <Button type="submit">Confirm</Button>

    Contextmenu needs to be wrapped around dialog if it is required to be activated from context menu. This is unintutive and while there are sound reasons of why this is the case it still adds to developers inconvenience.

  • Lack of basic features: If you want to add "multiselect" you are on your own, neither radix-ui nor shadcn provides multiselect functionality in its component. Argument is its not easy to do it in "accessible" way so most developers end up doing it by themselves in non-accessible ways. These limitations require additional custom development or integration with other libraries to fill the gaps.
  • Usability issues on mobile/touch based devices Take a look at this image of select component on mobile. You need to touch twice to select a field. It almost feels like mobile/touch was afterthought.

    select on mobile

Using react aria with shadcn ui

React Aria, developed by Adobe, is another headless component library similar to radix-ui that is ARIA compliant and focuses on covering range of devices such as desktop/mobile/touch enabled devices in accessible way. It has better support on mobile and code is developer friendly as well. Like radix-ui components are unstyled and can be styled according to your design.

Jolly-ui: shadcn style with react aria

Jolly-Ui is a new library that leverages React Aria under the hood while utilizing Shadcn styles. Jolly-Ui takes a similar approach to Shadcn, where code is copied into your project instead of adding it as a dependency. This method ensures that you retain full control over your components while benefiting from the accessibility features of React Aria.

Jolly-Ui focuses on modifying the interactive components of Shadcn, such as buttons, dialog, and modals, to enhance accessibility using React Aria. The display components of Shadcn, like cards and typography, are used as-is, maintaining the visual appeal while improving interaction accessibility.

Lets see same select example with jolly ui

select on mobile


If you are using shadcn and want better support for touch enabled devices add jolly-ui on top of shadcn to utilize react aria components with shadcn style.


Introduction to Tanstack Query and organizing code with queryOptions for maintainability
··4312 words·21 mins
TLDR; Introduction to tanstack query and organizing apis with queryoptions for better maintainibility
Grouping, filtering and aggregation in Tanstack table
·1942 words·10 mins
Tanstack-Table React
TLDR; Grouping, aggregation, filtering, pagination of data in tanstack table without user input
How to add custom styling in tanstack react table
··1983 words·10 mins
Tanstack-Table React
TLDR; How to use tanstack table in react and add custom styling with meta column definitions
Comparison of astro themes for saas 2024
·854 words·5 mins
TLDR; Comparison of Astro themes for SAAS marketing site and selecting best theme
How to add search to a website using flexsearch
·2373 words·12 mins
TLDR; Describes how to implement local search using flexsearch js library to website
What happens when your article gets on second page of hackernews - 2024
·958 words·5 mins
Hn Analytics
TLDR; Details of traffic volume and other insights when page is featured on hackernews and authors lame attempt at humor