Skip to content
All comparisons
Compare · otf-kit vs Tamagui

otf-kit vs Tamagui — primitives vs full design system

Pick Tamagui if you want raw primitives and full control to design every component yourself. Pick otf-kit if you want Tamagui's cross-platform engine plus designed native components, a Radix-based web package, and a full-stack kit.

Competitor
Best for
React Native developers · Cross-platform startups · Teams comparing primitive layers vs designed kits

TL;DR

Tamagui is the engine behind otf-kit's React Native side. It's the cross-platform styling system that solved the "Tailwind for React Native" problem before NativeWind existed — single style API, true compile-time optimization, parity primitives across web and native.

The honest comparison isn't "Tamagui or otf-kit" — it's "do you want to assemble the design layer yourself, or use one we already shipped?" Tamagui gives you the engine and ~30 unstyled primitives. otf-kit ships 85+ designed native components on top, plus 17 themes, plus a Radix-based web package, plus paid kits.

Feature matrix

otf-kitTamagui
LayerFull design systemEngine + primitives only
PlatformsWeb + iOS + AndroidWeb + iOS + Android
Component count150+ web · 85+ native~30 primitives
Designed themes17 picker-driven themesTheme system + a single starter
Compile-time optimizationInherits Tamagui's static extractionYes — the original implementation
Web renderingRadix primitives where usefulTamagui primitives
Full-stack kits6 live kits at $99 each: SaaS Dashboard, Fitness, Arcade, Booking, Marketplace and AI Agent. Sign-in and a database in every kit except ArcadeNone
PricingSDK free · Kits $99 eachFree, MIT

When Tamagui wins

  • You want to build your own design system from scratch on the cross-platform engine. Tamagui's createTokens + styled() API is the canonical path.
  • You want the smallest possible runtime — using just Tamagui's primitives gives you the leanest universal RN+web bundle.
  • You're a library author building reusable cross-platform components.
  • You don't need themes or kits — engine + primitives is enough.

When otf-kit wins

  • You want 85+ designed native components out of the box, not just primitives. We did the design work.
  • You want 17 swappable themes picker-driven (Mono, Ocean Teal, Warm Amber, Cosmic Night, and others), not a tokens object you fill in yourself.
  • You want a Radix-based web package that shares component names and design tokens with the native side. Tamagui can render to web but Radix is more battle-tested for web accessibility.
  • 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.

What's identical

The React Native side of otf-kit IS Tamagui under the hood. Every native component uses styled() from @tamagui/core, the theme system is Tamagui's, the cross-platform compilation is Tamagui's. If you've used Tamagui, the otf-kit native API will feel native within minutes.

If you need to drop down to raw Tamagui for something custom, you can — @tamagui/core is a peer dependency.

Code comparison — Button on native

// Tamagui — primitive, you bring the design
import { Button } from 'tamagui'

<Button size="$4" theme="active">Click me</Button>
// otf-kit — Tamagui primitive + designed shell
import { Button } from '@otfdashkit/ui-native'

<Button variant="primary" size="$4">Click me</Button>

The web side trades Tamagui for Radix:

// otf-kit on web
import { Button } from '@otfdashkit/ui'

<Button variant="default" size="lg">Click me</Button>

Same component name, different props. Native Button takes variant of primary, default, outlined, transparent, floating, destructive or shimmer, plus a Tamagui size token. Web Button takes variant of default, secondary, outline, ghost, destructive, link, gradient, texture or shimmer, and size of sm, default, lg, xl, icon or icon-sm.

When you want both

It's not "either-or" — most teams use otf-kit's designed components for the 80% case and drop to raw Tamagui when they need a custom interaction. Both ship side by side and share the same theme tokens.

FAQ

Why Radix on web instead of Tamagui's web target? Tamagui can render to web, but Radix has been the accessibility/keyboard-nav standard for years on web specifically. Using Radix on web + Tamagui on native gets us the best-of-both — Radix's web pedigree, Tamagui's RN pedigree.

Can I write Tamagui styled() components alongside otf-kit? Yes — they share the same theme tokens. You can wrap otf-kit components in Tamagui's styled() factory.

Does otf-kit's themes work with raw Tamagui components? Yes — both consume the same createTokens() output. Drop a <Theme> from @tamagui/core and otf-kit components inherit it.

Engine + primitives vs the designed kit we shipped

otf-kit is built on Tamagui for native — plus designed components, themes, a Radix-based web package, and full-stack kits. Tamagui is the cross-platform styling engine and unstyled primitives — assemble the design system yourself.

Everything Bundle — $149
Fitness Kit — $99 — Auth, DB, workouts — live demo ready

Live demos: SaaS Dashboard · Fitness · Arcade · Booking · Marketplace · AI Agent

See full pricing · Free SDK on GitHub →

Free with your email

Get the free AI configs pack

The AI files every kit ships with. Drop them in and your AI tool knows your project.

  • CLAUDE.mdProject context
  • .cursorrulesRules for Cursor
  • prompts/Task prompts

No spam. Unsubscribe any time.