Skip to content

Showcase & native preview

The public BeeUI Showcase is the same Expo application used by repository Web/native verification. It is not a docs mock and the docs do not bundle a second React Native runtime. Component pages deep-link with ?component=<registry-family>; pattern pages deep-link with the canonical source identity and the public router resolves it against the real Pattern Catalog.

Prerequisites: none to browse /showcase/; a BeeUI checkout and Node.js/pnpm are needed only for the pnpm --filter @beemvp/beeui-showcase ... commands below.

  • Component Gallery — interactive public component system.
  • Pattern Gallery — production screen patterns and demo states.
  • Generated component/pattern pages use embed=1 so the same runtime can sit inside docs without duplicate global chrome.
  • The public export is hosted under /showcase/; Expo’s experiments.baseUrl is enabled only for this launch build, so existing root-hosted CI/visual exports keep their current contract.

From a BeeUI checkout:

Terminal window
pnpm --filter @beemvp/beeui-showcase build:web:public

This stamps the current Git SHA and writes the subpath-ready static build to apps/showcase/dist-public-web/. The ordinary build:web remains the root-hosted CI/export path.

Run the same source tree rather than treating the Web Showcase as native proof:

Terminal window
# Expo dev server / QR
pnpm --filter @beemvp/beeui-showcase start
# Native local builds
pnpm --filter @beemvp/beeui-showcase ios
pnpm --filter @beemvp/beeui-showcase android
# Bundle-only evidence (not device runtime)
pnpm --filter @beemvp/beeui-showcase bundle:ios
pnpm --filter @beemvp/beeui-showcase bundle:android

start can load the bundle on a compatible Expo development path; ios/android invoke native local builds. Bundle/export/compile evidence proves packaging and resolution, not keyboard, safe area, hardware Back, VoiceOver/TalkBack or visual runtime behavior. Those claims require the repository’s explicit native runtime/device evidence classes.

The Showcase application version is aligned to the current BeeUI workspace release label, and the launch Web export injects git rev-parse --short HEAD. A public Showcase URL does not by itself imply npm publication — check Release & security or docs/dist-tag-policy.md for the current publication state instead of inferring it from the Showcase being reachable.

Outside embedded mode, Showcase includes lightweight navigation back to BeeUI Docs, Demo and the landing page. Native keeps its router-free application architecture; opening a public-site destination uses the system browser rather than introducing a navigation framework into BeeUI.