iOS
Native React Native behavior, safe-area ownership, native overlays, Dynamic Type evidence.
Unpublished · v20260902.0.0
Build native-first product UI without rebuilding the system around it.
BeeUI is a mobile-first React Native UI system for Expo, bare React Native, and Web — with explicit accessibility, responsive, theming, and production-pattern contracts.
Public npm/CLI publication is not open yet. Evaluate the real repository, Showcase, demo, package-boundary fixtures, or source-ownership workflow today.
$ corepack enable
$ pnpm install --frozen-lockfile
$ pnpm showcase
# production gates
$ pnpm check
$ pnpm release:verify37production pattern screens
3public package boundaries
Native + Webone behavior contract
Source-ownableRegistry workflow
Platform contract
Native first. Web supported deliberately.
One component system with platform differences documented instead of hidden behind “cross-platform” marketing.
Android
Native controls, back behavior, TalkBack-oriented contracts, emulator/device smoke lanes.
Web
React Native Web with keyboard/focus contracts, browser integration and deterministic visual QA.
Expo & bare RN
Showcase on Expo plus package-installed clean-consumer verification for bare React Native.
Components
Primitives that carry behavior, not product assumptions.
Layout, forms, selection, navigation, disclosure, overlays, data display, feedback, and application chrome share semantic tokens and explicit ownership boundaries.
Browse the generated component reference →Account settingscompact
BeeUI LibraryProduction account pattern
ThemeSystemLightDark
Densitycomfortable
Production patterns
From primitives to real product screens.
01
Authentication & onboarding
Sign-in, recovery, verification, onboarding and profile setup states.
Open in Showcase → 02Dashboard & finance
Information-dense cards, transactions, analytics and responsive dashboards.
Open in Showcase → 03Commerce & social
Catalog, checkout, messaging, feeds and interaction-heavy mobile flows.
Open in Showcase → 04Account & settings
Preferences, security, notifications and cross-platform settings surfaces.
Open in Showcase →Reference application
A coherent app, not another component gallery.
The production demo owns routing, mock service seams, application preferences, and realistic Dashboard, Records, Detail/Edit, Schedule, and Settings flows.
DashboardRecordsDetail / EditScheduleSettings
Accessibility
Evidence has a label.
Deterministic semantics, keyboard/focus, RTL, reduced motion, large text and native compilation are separated from device/runtime evidence. Web previews are never presented as native proof.
Accessibility contract →Responsive
Mobile-first is enforced.
Shared breakpoint tokens and responsive primitives keep compact layouts primary while scaling deliberately to medium and expanded widths.
Responsive guide →Theming & density
Brand the semantics, keep the behavior.
Light/dark semantic tokens, brand overrides and density modes are downstream of a stable behavior contract.
Choose your ownership model
Package boundary or source ownership.
Keep BeeUI behind public exports.
The Showcase/demo and clean-consumer fixtures exercise the intended package boundary through workspace and packed-artifact verification while public npm publication is closed.
Evaluate the package shape →Own the source you ship.
Inspect, add, diff and update component source through BeeUI's repository-local Registry workflow without creating a second behavior contract.
Source ownership guide →AI-native discovery
Give agents the same canonical context.
`llms.txt`, component/pattern feeds and the agent cookbook are generated and freshness-checked from repository truth.
Release truth
Release-ready engineering is not the same as published distribution.
Current workspace version: 20260902.0.0. Public distribution status: Unpublished. The website exposes what exists today without opening npm, GitHub Release/tag, dist-tag, or owner-gated publication actions.
Release & security guidance →