BeeUI Docs
BeeUI is a production-oriented React Native UI system with one public behavior contract across Expo, bare React Native and Web.
The release status above states the current npm publication truth. During the
0.86.2 prerelease line latest follows the newest complete, verified RC only after the owner moves it
for all four packages, so it can lag next; the last observed latest target is recorded in
docs/dist-tag-policy.md.
Use @next or the exact RC version in install commands; that stays correct while latest lags
next and after the stable 0.86.2 promotion.
npm install @beemvp/beeui-ui@next @beemvp/beeui-core@next @beemvp/beeui-tokens@nextnpx @beemvp/beeui-cli@next --helpUse the search box at the top of any page to jump straight to a component, token, CLI command or error message.
Prerequisites: none — this is the entry point. New to BeeUI? Go to Start next.
What do you want to do?
Section titled “What do you want to do?”| I want to… | Go to |
|---|---|
| Get BeeUI rendering in my app for the first time | Start — Expo, bare React Native or Web |
| Look up a component’s props, types or behavior | Components |
| Copy a whole screen composition | Production patterns |
| Achieve a specific outcome — theming, density, tables, dates | Guides |
| Understand why BeeUI works the way it does | Learn |
| Find an exact token, symbol, command or Registry item | Reference |
| Fix an error I am seeing right now | Troubleshooting |
| See it running before I commit to anything | Showcase · Demo app |
| Own the source instead of depending on a package | CLI & source ownership |
| Build against BeeUI with an AI agent | AI & LLM surfaces |
The four documentation modes
Section titled “The four documentation modes”BeeUI splits documentation by what you need in the moment, so the same subject can appear in more than one place without contradicting itself.
| Section | Answers | Shape |
|---|---|---|
| Start | “How do I get a first result?” | one verified path per platform |
| Guides | “How do I achieve X?” | task, action, verification |
| Learn | “Why does it work this way?” | concept, invariants, consequences |
| Reference | “What exactly is it called?” | derived from source, never prose-first |
Where a guide and a reference page disagree, the generated reference wins — it is derived from the package exports themselves.
Platform and release truth
Section titled “Platform and release truth”- Current RC: see the release status at the top of this page.
- Default channel: during the
0.86.2prerelease linelatestfollows the newest complete, verified RC once the owner moves it for all four packages, so it can lagnext; its last observed target is recorded in the dist-tag policy and re-verified after every publish. It moves to the stable version, and never returns to a prerelease, at the0.86.2stable promotion. Seedocs/dist-tag-policy.md. - Current compatibility — the tested and pinned versions, machine-checked.
- Migration & versioning — channel, version authority and upgrade rules.
- Release & security — reporting path and source-ownership implications.
- Accessibility · Responsive · Performance · Architecture
BeeUI distinguishes evidence classes and never infers a stronger one from a weaker one: type and contract checks, bundle and native compile, browser interaction, and simulator or device runtime. Each page states which class backs its claims.
For maintainer contracts, source history and exact evidence records, the public repository remains
the authority: docs/.