appCN
appCN
Copy-paste mobile components for React Native + Expo.
A shadcn-philosophy library: you own the source, NativeWind styles the surface, Reanimated drives the motion — and the featured AI-native collection ships streaming bubbles, prompt composers, reasoning traces, and a reactive 3D voice orb.
Browse components · CLI docs · Mobile app · Live showcase · GitHub
Quick start
The CLI handles NativeWind + Reanimated wiring and registers the @app-cn
shadcn namespace for you. One command to set up, one to add a component.
# 1. (Recommended) One-shot project setup
npx @app-cn/cli@latest init
# 2. Add any component by slug
npx @app-cn/cli@latest add voice-spherePrefer your own pipeline? appcn add is a thin wrapper around shadcn — you can
skip the CLI entirely:
# Copy a single component via shadcn (no setup, one-off)
npx shadcn@latest add https://appcn.vercel.app/r/voice-sphere.json
# Or pull the whole library as a managed dep
npm install @app-cn/uiBuilding with an AI agent? Add the appCN MCP server so Claude Code, Cursor, or Windsurf can discover and install components for you — and write new code in appCN's motion/haptic style:
# Claude Code
claude mcp add appcn -- npx -y @app-cn/mcpSee MCP docs for Cursor / Windsurf / VS Code config.
Status: v0.1.0 live on npm. Five components shipped — the AI collection is the marketed wedge and is the first place to land new work.
Related MCP server: MCP Server Starter Template
What's in the box
New: appCN is live on real phones — scan a QR with Expo Go and the entire component gallery loads on Android or iPhone in seconds. No emulator, no developer account. Standalone Play Store APK is in review — shipping soon.
Base
Component | Delight |
| Spring-y press scale to 0.96, settles in 140 ms — feels weighted, never twitchy |
AI-native
Component | Delight |
| Three-phase thinking → token stream → settle |
| Send morphs into a stop with a spinning ring |
| Auto-collapses the instant the answer lands |
| Reactive 3D orb that breathes with voice level |
Every component has an interactive web preview, a QR you can scan with Expo Go to run it live on your phone, and a video — same code path on every surface. → appcn.vercel.app/components
Why appCN
Real-phone previews. Scan a QR with Expo Go and the component runs live on your device with native gestures. No emulator gymnastics.
AI-native flagship. The AI collection is the wedge — components built for AI apps that nobody else ships well.
Quadruple distribution. The
appcnCLI, the shadcn registry,@app-cn/uifrom npm — or the MCP server, so your AI coding agent installs components for you. Same primitives, your call.Motion-first defaults. Reanimated + gesture-handler, shared motion tokens (
duration/easing/spring), one delight detail per component.Dark-mode first. Designed dark, then derived to light. Premium reads as depth, not rainbows.
You own the source. Copy-paste philosophy means no lock-in — once a component lands in your repo, edit freely.
Documentation
Surface | What's there |
Live docs site — landing, every component, live previews | |
| |
Play Store + Expo Go install paths, deep-link contract | |
Architecture, monorepo map, commands, Metro/Reanimated gotchas | |
Taste layer — motion rules, the "one delight detail" rule, the 8-step SOP | |
Dev setup, the Changesets release flow, PR conventions | |
Cross-tool guide for AI coding agents (Claude / Cursor / Windsurf / Codex / Aider) |
Contributing
Every new component ships through the 8-step SOP in DESIGN.md → Component checklist. Don't skip steps — the PR template enforces them and a missing changeset blocks the release pipeline.
Working with an AI agent? Invoke the /new-component Claude skill — it
walks the checklist, drops a typed <slug>.meta.ts template ready to fill,
wires the registry + showcase entries, and verifies with typecheck + registry
build.
Full guide: CONTRIBUTING.md.
Releases
Releases are driven by Changesets and published to npm via OIDC Trusted Publishing — zero long-lived secrets.
pnpm changeset # describe what changed + pick a bump
git commit -am "..." # commit the changeset alongside your code
# Open a PR. After merge to main, a "Version Packages" PR opens automatically.
# Merge that PR → CI publishes via OIDC.Every published version gets a verified provenance badge on npm.
Deploying
Project | Vercel root directory | What it serves |
Docs |
| Landing, |
Showcase |
| Expo web export — the iframe target for interactive previews |
Deploy order (matters):
Deploy the showcase first (
apps/showcase) so you have a URL.Deploy the docs, setting
NEXT_PUBLIC_SHOWCASE_WEB_URLto that URL.Optional: custom domains (
appcn.vercel.app→ docs,appcn-showcase.vercel.app→ showcase).
Required env vars (docs project):
Variable | Value |
|
|
| (empty for v1 — needs EAS Update for the QR tab) |
|
|
The showcase project needs no env vars. Defaults live in
apps/web/.env.example.
Acknowledgments
Inspired by shadcn/ui's copy-paste philosophy and react-native-reusables's docs-site polish. Built on top of NativeWind, Reanimated, and Expo.
License
MIT — you own the code.
Maintenance
Related MCP Servers
- AlicenseCqualityDmaintenanceMCP server for searching npm packagesLast updated111116MIT
- Alicense-qualityDmaintenanceA comprehensive template for building MCP servers that expose UI component registries and design systems to AI assistants. It enables users to browse, fetch, and retrieve implementation details from registries following the shadcn/ui format.Last updated1432MIT
- AlicenseBqualityDmaintenanceMCP (Model Context Protocol) Server for skill4agent - Search, view, and install AI skills in AI conversations.Last updated3503MIT
- AlicenseAqualityCmaintenanceMCP server that exposes the @bunge/ds-components design system catalog, allowing AI assistants to list, search, and retrieve component details including inputs, outputs, usage examples, and import instructions.Last updated4MIT
Related MCP Connectors
MCP server for accessing curated awesome list documentation
MCP server for hex.pm and hexdocs.pm: search, inspect, compare, and audit Elixir packages
MCP (Model Context Protocol) server for Appwrite
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Salah-XD/appCN'
If you have feedback or need assistance with the MCP directory API, please join our Discord server