Skip to main content

HeroUi v3

@Junior Garcia , I’m not happy with this decision. With the new version, you’re removing the personal touches you added from v1 to v2. You built everything yourself — the animations, the props — and now in v3 you’re replacing them with Radix UI primitives and its variants. You used to set the example in the market; now it feels like we’re just the same as everyone else because another platform is popular for using primitives. But popularity doesn’t mean better. Even they look to your project for inspiration. The animations and Tailwind variants you created were amazing. If v3 loses those unique elements, it feels like that would be their victory, not yours.

9 comments

Log in to comment and vote

Comments9

  • Junior Garcia

    Team•

    Nov 6, 2025

    Hey check out the just launched beta version https://v3.heroui.com/

  • Junior Garcia

    Team•

    Oct 24, 2025

    Hey we’re iterating quickly, we just released a new post for what’s next on the look & feel of HeroUI v3

    https://x.com/hero_ui/status/1981373562477842869

    You can also share your thoughts on this post and help us shape the v3 API

    https://github.com/heroui-inc/heroui/discussions/5837


    Our vision with v3 is make it feels unique but at the same time really customizable (pain point on v2) portable and adaptable, that’s why we are building on top of RAC primitives instead of hooks and exporting each slot separately

    • cam

      •

      Oct 28, 2025

      Migrating from v2 to v3 is a major change, and I’ll need to spend quite a bit of time refactoring my project. I’m just curious why didn’t you use React Aria Components from v2?

      • Junior Garcia

        Team•

        Nov 6, 2025

        We’re still using RAC, but the components not the hooks (way more complex)

  • usse

    •

    Sep 26, 2025

    v1 and v2 use react-aria-componentes, v3 too, wdym?

    https://v3.heroui.com/docs/introduction#why-react-aria-over-radix