Delacour UI vs React Native Reusables

Two answers to shadcn/ui for React Native.

Both libraries copy a component's source into your app and paint it from shadcn's CSS variables. React Native Reusables ports shadcn/ui's core set onto @rn-primitives, runs on the web too, and uses the shadcn CLI. Delacour UI is native only, Tailwind v4 through Uniwind, and covers far more ground — charts, sheets, toasts, date pickers — with an upgrade path for files you have edited.

How the code arrives

Both are the shadcn model: the source lands in your repository and is yours to change. They differ in what happens after.

Component source in your repository

Yes

Delacour UI

delacour add button

Yes

React Native Reusables

npx @react-native-reusables/cli add button

Runs on the shadcn CLI

No

Delacour UI

its own CLI, delacour

Yes

React Native Reusables

uses the shadcn CLI under the hood

Also installable as one npm package

Yes

Delacour UI

@delacour/react-native-ui, one subpath per component

No

React Native Reusables

copy only

Upstream fixes merge into a file you edited

Yes

Delacour UI

delacour update merges into your copy

No

React Native Reusables

add --overwrite replaces the file

Scaffolds a new Expo app

No

Delacour UI

delacour init sets up an app you already have

Yes

React Native Reusables

init, with minimal, minimal-uniwind and clerk-auth templates

Styling and theming

Both speak shadcn's token names. They sit on different Tailwind generations.

Tailwind className on native

Yes

Delacour UI

Tailwind v4, compiled by Uniwind

Yes

React Native Reusables

Tailwind v3 through NativeWind, or Uniwind

Works with NativeWind

No

Delacour UI

Uniwind only — the two cannot share an app

Yes

React Native Reusables

NativeWind or Uniwind, detected by the CLI

shadcn's token names

Yes

Delacour UI

--primary, --muted-foreground, --radius

Yes

React Native Reusables

shadcn/ui's CSS variables in global.css

Bring a web app's globals.css across

Yes

Delacour UI

delacour theme takes a path, a URL or stdin

Partly

React Native Reusables

paste a Tailwind v3 theme, rename .dark to .dark:root, mirror it in theme.ts

A visual theme builder

Yes

Delacour UI

/theme, on this site

Partly

React Native Reusables

points to shadcn/ui's themes page

What is in the box

Reusables mirrors shadcn/ui's core primitives. Delacour UI carries those plus the mobile components an app reaches for next.

Components

Yes

Delacour UI

108, grouped from actions to overlays

Partly

React Native Reusables

30, shadcn/ui's core set

Charts, bottom sheet, toast, date picker, carousel

Yes

Delacour UI

each one, on headless Skia and sheet engines

No

React Native Reusables

not in the component list

Radix-style primitives underneath

No

Delacour UI

its own compound parts

Yes

React Native Reusables

@rn-primitives, a port of Radix UI's API

Runs on the web as well

No

Delacour UI

iOS and Android only

Yes

React Native Reusables

universal apps, through react-native-web

Coding agents

Both expect an agent to do the adding. They hand it different things.

An MCP server for your project

Yes

Delacour UI

npx delacour@latest mcp

Partly

React Native Reusables

catalogs.dev, a separate Founded Labs product

Every docs page as Markdown

Yes

Delacour UI

/llms.txt, /llms-full.txt and a .md twin per page

Partly

React Native Reusables

the docs are MDX in the public repository

A track record

Partly

Delacour UI

a young library, one maintainer

Yes

React Native Reusables

8.7k GitHub stars, in Vercel's OSS programme

Which one

Choose React Native Reusables if you need the web from the same components, are staying on NativeWind, or want shadcn/ui's exact primitives and nothing more.

Choose Delacour UI for a native app that needs more than the core set, a theme carried across from your web app in one command, and copies you can edit without losing upgrades.

Sources

Every row on React Native Reusables's side was read from these pages on 2026-11-04. If one is out of date, open an issue and it will be corrected.