otf-kit vs NextUI / HeroUI — picking a UI library in 2026
Pick HeroUI if you want a single beautifully-designed default theme on web. Pick otf-kit if you need 17 swappable themes, a React Native package, or a kit with auth and a database wired; payments are not included.
TL;DR
NextUI rebranded as HeroUI in 2024. It's a beautifully-designed React UI library built on Tailwind + React Aria, with a strong default aesthetic and good DX. The catch: web-only, one default theme, no full-stack kits.
otf-kit is built on similar foundations on web, adds a native package, and ships 17 swappable themes out of the box, has a React Native package, and pairs with paid kits that include the full backend.
Feature matrix
| otf-kit | HeroUI (NextUI) | |
|---|---|---|
| Platforms | Web + iOS + Android | Web only |
| Component count | 150+ web · 85+ native | ~50 web |
| Themes | 17 picker-driven themes | 1 default theme + dark mode |
| Underlying primitives | Radix (web) · Tamagui (native) | React Aria |
| Styling engine | Tailwind v3 (v4 also supported) | Tailwind + tailwind-variants |
| Full-stack kits | 6 live kits at $99 each: SaaS Dashboard, Fitness, Arcade, Booking, Marketplace and AI Agent. Sign-in and a database in every kit except Arcade | None |
| Animation | Motion + GSAP integrations | Framer Motion (built in) |
| Pricing | SDK free · Kits $99 each | Free, MIT |
When HeroUI wins
- You love the HeroUI default look — it's genuinely beautiful out of the box, and the team behind it has strong taste.
- You want animation built in to every component without extra config.
- You're web-only and the React Native question doesn't apply.
- You don't need theme variety — one strong default is enough.
When otf-kit wins
- You need multiple themes (Mono, Ocean Teal, Warm Amber, Cosmic Night, and other token themes) — picker-driven, runtime-swappable.
- You're shipping cross-platform. HeroUI doesn't run on RN.
- You want a full-stack starting point — SaaS Dashboard, AI Agent, Fitness, Booking and Marketplace include a backend and sign-in; Arcade runs client-side by default.
- You need broader component coverage — 240+ components vs HeroUI's ~50.
Code comparison — Button
// HeroUI
import { Button } from '@heroui/react'
<Button color="primary" variant="solid">Click me</Button>// otf-kit
import { Button } from '@otfdashkit/ui'
<Button variant="default">Click me</Button>Migrating from HeroUI to otf-kit
The mental model is similar — both lean on Tailwind variants + a token system. Migration steps:
bun add @otfdashkit/ui @otfdashkit/tokens- HeroUI's
sizeandvariantprops have otf-kit counterparts with different value sets; check each component's page for the rest. - Animations: HeroUI's built-in motion → otf-kit ships Motion presets you wire per-component.
- Use the Design Token Migrator → to convert HeroUI's theme tokens.
FAQ
Is HeroUI's animation a deal-breaker without it in otf-kit? otf-kit doesn't enforce animations — we ship Motion (Framer Motion's React-only fork) as a peer dependency and provide presets for hover / tap / page transitions. You opt in per surface; it's not built into every component.
Does otf-kit use React Aria? On web, otf-kit uses Radix. Both Radix and React Aria solve the same problem (accessible primitives) — the difference is mostly community and governance. Behavior is equivalent for typical use.
What about the HeroUI Pro template kit? HeroUI Pro is a separate paid product. otf-kit's kits are equivalent in scope but tend to be more full-stack (auth and a database wired) than HeroUI's templates.
One beautiful theme vs owned kits + themes
otf-kit is an owned full-stack kit — 17 themes, a React Native package, auth and a database wired. HeroUI (NextUI) is a beautifully designed web-only Tailwind UI library — components and a strong default aesthetic, not a backend kit.
Everything Bundle — $149
SaaS Dashboard — $99 — 12 screens; billing is not included
Live demos: SaaS Dashboard · Fitness · Arcade · Booking · Marketplace · AI Agent