HeroUI
Tailwind components built on React Aria.
HeroUI, formerly NextUI, pairs React Aria Components for behaviour with a polished Tailwind theme. You get Adobe-grade keyboard and screen reader handling without designing or styling anything.
At a glance
| Install | npm install @heroui/react |
| Primitives | React Aria Components |
| Styling | Tailwind CSS v4 |
| Requirements | React 19 or later, hard floor |
| Also ships | React Native components in v3 |
| MCP server | yes, two of them |
| License | MIT |
Requirements are hard floors
React 19 and Tailwind v4 are not recommendations. An older project needs upgrading before HeroUI will install cleanly, and that upgrade is usually the larger piece of work.
What the code looks like
Components are built from customisable parts with fully typed APIs, so editor autocompletion is genuinely useful rather than a list of any.
import { Button, Modal, ModalContent, ModalHeader } from "@heroui/react"
<Button color="primary" variant="solid" radius="md">
Deploy
</Button>
Web and mobile from one design language
v3 ships React Native components alongside the web ones. A design language can travel from a marketing site to a native app without maintaining two separate libraries, which almost nothing else here offers.
Two MCP servers, and the second one matters
One exposes the v3 documentation to an assistant. The other carries the v2 to v3 migration guides specifically. If you are coming from NextUI or HeroUI v2, that second server does real work, because a migration is exactly where an assistant otherwise invents APIs from stale training data.
Choose it if
- You want React Aria's accessibility with a finished look out of the box.
- You are on React 19 and Tailwind v4 already.
- You ship web and React Native from one design system.
Look elsewhere if
- You cannot upgrade to React 19. That is not negotiable here.
- You want a neutral base. The default look is distinctive and recognisable.