Delacour UI vs BNA UI

Same delivery, different styling layer.

Both libraries are shadcn-inspired and copy each component's source into your app through a CLI, with an MCP server and Markdown docs for agents. BNA UI styles with StyleSheet objects and a colours file of its own, and ships camera, audio and video components plus backend starters. Delacour UI styles with Tailwind classes painted from shadcn's CSS variables, so a web app's theme carries straight across.

How the code arrives

Both copy the source in. Only one also ships as a package.

Component source in your repository

Yes

Delacour UI

delacour add button

Yes

BNA UI

npx bna-ui add button

Also installable as one npm package

Yes

Delacour UI

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

No

BNA UI

fetched from ui.ahmedbna.com/r by the CLI

Starter apps with a backend wired in

No

Delacour UI

delacour init sets up an app you already have

Yes

BNA UI

init, convex, supabase and firebase starters

Bare React Native, without Expo

Yes

Delacour UI

Expo or the React Native CLI

Partly

BNA UI

installation covers Expo apps only

Styling and theming

The real difference. One is Tailwind on shadcn's tokens; the other is StyleSheet on its own.

Tailwind className

Yes

Delacour UI

Tailwind v4, compiled by Uniwind

No

BNA UI

StyleSheet and the style prop, never className

No styling compiler in your Metro config

No

Delacour UI

Uniwind wraps Metro

Yes

BNA UI

plain StyleSheet, nothing to configure

shadcn's token names

Yes

Delacour UI

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

No

BNA UI

its own theme/colors.ts, read with useColor

Bring a web app's globals.css across

Yes

Delacour UI

delacour theme takes a path, a URL or stdin

No

BNA UI

colours are re-typed into theme/colors.ts

Light and dark

Yes

Delacour UI

both, from one theme.css

Yes

BNA UI

built-in light and dark mode

What is in the box

Similar breadth, aimed at different apps.

Components

Yes

Delacour UI

108, grouped from actions to overlays

Yes

BNA UI

52, plus a separate chart set

Charts, bottom sheet, toast, date picker

Yes

Delacour UI

each one

Yes

BNA UI

each one

Camera, audio and video components

No

Delacour UI

not in the library

Yes

BNA UI

camera, audio recorder and player, video

Runs on the web as well

No

Delacour UI

iOS and Android only

Yes

BNA UI

responsive web support

Coding agents

Both are built for an agent to drive — the closest row on the page.

An MCP server

Yes

Delacour UI

npx delacour@latest mcp

Yes

BNA UI

npx bna-ui mcp

Every docs page as Markdown

Yes

Delacour UI

/llms.txt and a .md twin per page

Yes

BNA UI

/llms.txt and a .md twin per page

An installable agent skill

Yes

Delacour UI

npx delacour@latest skills

Yes

BNA UI

a Claude skill

Which one

Choose BNA UI if you would rather not run a styling compiler, need camera, audio or video components, want a backend starter, or need the web.

Choose Delacour UI if your team already writes Tailwind and shadcn/ui on the web and wants the native app on the same classes and the same theme.

Sources

Every row on BNA UI'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.