Skip to content

Switch

Controlled native switch with semantic track/thumb colors; enabled usage without onValueChange warns in development.

  • Category: Forms & selection
  • Status: stable public Registry/export-map component family
  • Targets: iOS · Android · Web, subject to the compatibility contract
  • Prerequisites: @beemvp/beeui-ui installed (or this component’s source copied via the Registry CLI below) and, on Web, the BeeUI Tailwind/Uniwind theme CSS loaded — see Start for full platform setup.
  • Source: packages/ui/src/components/switch.tsx
import { Switch } from '@beemvp/beeui-ui';

There is no documented deep/private source import. For source ownership from a BeeUI checkout:

Terminal window
pnpm beeui add switch

Registry (used throughout this page) is BeeUI’s source-ownership manifest — registry/registry.json — that the pnpm beeui/@beemvp/beeui-cli CLI reads to copy a component’s real source into your app and rewrite its internal imports; it is not an npm package index. This component’s own Registry entry: registry/registry.json.

  • Primary export: Switch
    • Also routed here, outside the Registry family:
      • switch
    • Package export subpath: @beemvp/beeui-ui/switch

Exported types: SwitchProps

The generated API inventory is mechanically joined to packages/ui/src/index.ts, Registry metadata, and the component reference contract. Each type’s field table below is parsed directly from that source, not a second hand-maintained copy; for the fuller behavior narrative see the canonical component behavior catalog.

Controlled native Switch (value/onValueChange); enabled usage without onValueChange warns in development instead of silently doing nothing.

This type adds no fields of its own. These are the props the implementation reads from the base type below; everything else is passed straight through.

Prop Default
accessibilityLabel —
accessibilityLabelledBy —
accessibilityState —
disabled false
onValueChange —
value false

Also carries every prop of Omit<RNSwitchProps, 'accessibilityRole' | 'role' | 'ios_backgroundColor' | 'thumbColor' | 'trackColor'> — that upstream contract is not reproduced here.

The executable fixtures below are the source-grounded usage examples; consumers should not infer state ownership from DOM structure or another UI library.

  • No additional provider is required by this family. BeeUIProvider remains the recommended application root.
  • Peer/native dependencies visible to this Registry item: react, react-native
  • Registry dependency closure: theme, use-required-callback-warning
  • Safe-area ownership remains explicit: shell surfaces touching system edges opt into SafeArea; components do not silently invent app-shell insets.
  • Web consumers load the BeeUI semantic theme CSS as documented in Web onboarding.

This family ships no platform-specific file, but its source branches on Platform, so some behavior differs by target.

The same public family is exposed across the supported target matrix; meaningful platform differences remain governed by the compatibility contract.

Evidence classes are not equal and this page does not blur them: Web behavior is exercised in a real browser, while iOS and Android carry package/export and native-compile evidence, which is not device-runtime proof. The compatibility contract records which class each claim rests on.

  • Roles this family assigns: switch (iOS and Android) — set in switch.tsx by the components themselves, not by the caller.
  • Accessibility states and properties it sets: accessibilityLabel, accessibilityLabelledBy, checked (iOS and Android), disabled (iOS and Android), labelledby (Web), required — read from switch.tsx.

Keyboard/focus behavior, announcements, Dynamic Type/Web zoom, RTL and reduced-motion expectations are not derived here — see Accessibility overview, Keyboard & focus, RTL/localization and Large text & zoom. BeeUI does not claim universal accessibility certification from automated tests.

  • Style axes: none of its own — its appearance comes from tokens and your own classes; it also carries Omit<RNSwitchProps, 'accessibilityRole' | 'role' | 'ios_backgroundColor' | 'thumbColor' | 'trackColor'>.
  • Class-name surfaces: none declared by this family; it also carries Omit<RNSwitchProps, 'accessibilityRole' | 'role' | 'ios_backgroundColor' | 'thumbColor' | 'trackColor'>.

Colors, spacing and typography come from semantic tokens rather than from values written here — see Theming and Density. A className is an escape hatch for source-owned and application work, not a cross-engine portability guarantee.

Each link below opens the Showcase at that exact example, not at the top of the gallery:

  • basic — smallest meaningful complete usage
  • composition — the composition example

The Showcase links demonstrate Web behavior; use the native-preview guide for real simulator/emulator/device paths.

This frame loads the real BeeUI Web Showcase on demand; it is not a second docs-only implementation. It proves browser behavior only. Use native preview for iOS/Android simulator, emulator or device paths.

  • Family root / primary export: Switch
    • Exported type surface:
      • SwitchProps

The tree above is ordinary document structure so it remains readable with keyboard and assistive technology; it is derived from the real public export family rather than a canvas-only diagram.

These are the parts of the typechecked runtime Showcase fixture behind this live preview — apps/showcase/component-gallery/component-gallery.tsx, 1103 lines — where Switch is actually used: 10 lines in 2 places. Each block is copied verbatim from the line range named above it, so it is the same executable source, not a retelling of it. The rest of that file exercises other families and is not reproduced here.

Imports the examples below need (a filtered subset of the fixture’s own top-level imports):

import { Switch } from '@beemvp/beeui-ui';
import * as React from 'react';

Fixture state this block reads (same file, line 461):

const [notifications, setNotifications] = React.useState(true);

lines 667–671:

<Switch
accessibilityLabel="Notifications"
onValueChange={setNotifications}
value={notifications}
/>

Fixture state this block reads (same file, line 461):

const [notifications, setNotifications] = React.useState(true);

lines 1074–1078:

<Switch
accessibilityLabel="Push notifications"
onValueChange={setNotifications}
value={notifications}
/>

Open the fixture itself for the full surrounding component. For a smaller app-specific example, start from the imports and fixture-state blocks above and keep only the state your screen owns.

Track and thumb colors come from tokens and cannot be set per instance — the three React Native color props are not accepted. On Web the component deliberately applies no role and no checked or disabled accessibility state of its own; it sets both on native only.