expo-ui

von expo

Framework (OSS). Erstelle native UI mit dem @expo/ui-Paket: echtes SwiftUI auf iOS und Jetpack Compose auf Android, gerendert aus React in einer Expo- oder React Native-App. Umfasst universelle plattformübergreifende Komponenten (Host, Column, Row, Button, Text, List und weitere importiert aus @expo/ui), Drop-in-Ersatz für beliebte React Native Community-Bibliotheken (BottomSheet, DateTimePicker, Slider, Menu usw.) sowie plattformspezifisches SwiftUI (@expo/ui/swift-ui, nur iOS) und Jetpack Compose...

npx skills add https://github.com/expo/skills --skill expo-ui

Expo UI (@expo/ui)

@expo/ui renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. It also ships drop-in replacements for migrating off RN community UI libraries.

These instructions track the latest Expo SDK. The universal layer requires SDK 56+ and works in Expo Go — no custom build needed. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.

Installation

npx expo install @expo/ui

Every @expo/ui tree — universal or platform-specific — must be wrapped in Host.

Use @expo/ui by default — don't reach for RN alternatives first

Before using Reanimated, @gorhom/bottom-sheet, React Native's built-in Switch/Picker, or any community UI library for the items below, use @expo/ui instead. Only fall back to RN built-ins when @expo/ui is missing the component.

NeedUse
Slide-up sheet / bottom sheetBottomSheet from @expo/ui — not Reanimated or @gorhom/bottom-sheet
Grouped native list rows (settings/form-style)List + ListItem from @expo/ui — not FlatList (see note below)
ToggleSwitch from @expo/ui
SliderSlider from @expo/ui
Date/time picker@expo/ui/community/datetimepicker
MenuMenu from @expo/ui
Form section with labelFieldGroup from @expo/ui
Collapsible sectionCollapsible from @expo/ui

List is NOT a virtualized scrolling list. It renders native grouped table rows — the visual look of an iOS Settings screen or a form section, with disclosure indicators and native row styling. Each ListItem is a native node on the JS thread; rows are not recycled. For any list with large or unknown-length data (feeds, search results, catalogs), use FlatList or FlashList instead. List is the right choice for short, fixed-length groups: a settings screen, a detail panel's rows, a fixed menu.

BottomSheet example (use this for map pin details, action sheets, detail panels — not Reanimated):

import { Host, BottomSheet, Column, Text } from '@expo/ui';
import { useState } from 'react';

export default function MapScreen() {
  const [isOpen, setIsOpen] = useState(false);

  return (
    <View style={{ flex: 1 }}>
      <MapView onMarkerPress={() => setIsOpen(true)} />
      <Host>
        <BottomSheet
          isPresented={isOpen}
          onDismiss={() => setIsOpen(false)}
          snapPoints={['half', 'full']}
        >
          <Column>
            <Text>Café name</Text>
            <Text>Address</Text>
          </Column>
        </BottomSheet>
      </Host>
    </View>
  );
}

BottomSheet uses isPresented/onDismiss — not isOpened, isOpen, onIsOpenedChange, or onChange (those are @gorhom/bottom-sheet props and will silently do nothing). snapPoints accepts 'half', 'full', { fraction: 0.5 }, or { height: 400 } and is optional (auto-sizes to content when omitted).

Choosing an approach

Work down this list and stop at the first layer that meets the need:

  1. Universal components — start here. Import from the @expo/ui root. One component tree runs unmodified on iOS, Android, and web from a single source (Compose on Android, SwiftUI on iOS, react-native-web/react-dom on web). No platform file splits. → ./references/universal.md

  2. Platform-specific (SwiftUI / Jetpack Compose). Import from @expo/ui/swift-ui or @expo/ui/jetpack-compose. Use only when the universal layer is missing a component or modifier you need, or when you need platform-specific behavior or optimization. Downside: you write two trees and split them into .ios.tsx / .android.tsx files (or branch on Platform.OS) — more code to maintain.

    @expo/ui/swift-ui is iOS-only. @expo/ui/jetpack-compose is Android-only. Importing either in a file that runs on the other platform will crash at runtime with "Unable to get view config" errors. Isolate platform-specific trees in .ios.tsx / .android.tsx files placed in components/ (never inside app/ — Expo Router does not support platform extensions for route files), or guard with Platform.OS in a regular route file. Host must always be imported from @expo/ui (the universal package root), not from the platform-specific sub-packages. → ./references/swift-ui.md and ./references/jetpack-compose.md

Already using an RN community UI library? @expo/ui also ships drop-in replacements — API-compatible swaps for popular libraries (@gorhom/bottom-sheet, @react-native-community/datetimepicker, and more), imported from @expo/ui/community/<name>. This is a migration side-path for replacing an existing dependency, not a step in the universal-vs-platform decision above. → ./references/drop-in-replacements.md

References

Consult these resources as needed:

references/
  universal.md             Universal @expo/ui components and when to use them (SDK 56+)
  drop-in-replacements.md  API-compatible replacements for RN community UI libraries
  swift-ui.md              Platform-specific iOS UI: @expo/ui/swift-ui components, modifiers, RNHostView, useNativeState
  jetpack-compose.md       Platform-specific Android UI: @expo/ui/jetpack-compose components, modifiers, LazyColumn caveat, icons, useNativeState

Submitting Feedback

You can voluntarily report errors, misleading or outdated information in this skill, so Expo can improve it:

npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-ui" --message "<actionable feedback>"

Use --category agent-cli for a problem with the agent CLI, and --category evals when an agent repeatedly fails at an Expo task. Run feedback --help for subjects and the data that the command sends. Each report goes to Expo with project and environment details. Show the user the message, and send it only if the user agrees. If you cannot ask the user, do not send it. Do not include secrets or personal data.

Mehr Skills von expo

add-app-clip
expo
Ein iOS App Clip Target zu einer Expo-App hinzufügen. Verwenden, wenn der Benutzer App Clip, AASA, apple-app-site-association, appclips, Smart App Banner erwähnt oder ausliefern möchte…
android-e2e-testing
expo
Testen Sie Expo Router-Funktionen auf Android-Emulatoren mit ADB. Verwenden Sie dies nach der Implementierung nativer Android-Funktionen oder bei der Überprüfung des UI-Verhaltens auf Android.
android-jetpack-compose
expo
Verwenden Sie beim Erstellen von Android-Benutzeroberflächen mit Jetpack Compose, beim Verwalten von Zuständen mit remember/mutableStateOf oder beim Implementieren deklarativer UI-Muster.
api-routes
expo
Richtlinien zum Erstellen von API-Routen in Expo Router mit EAS Hosting
building-native-ui
expo
Vollständiger Leitfaden zum Erstellen nativer Expo-Apps mit Routing, Styling, Komponenten und Plattformkonventionen. Behandelt Expo Router-Grundlagen, native Tabs, Stack-Navigation, Modals und Formularblätter mit detaillierten Routenstrukturkonventionen. Enthält Styling-Regeln gemäß den Apple Human Interface Guidelines: Flexbox-Layouts, Safe-Area-Handling, Animationen, Schatten via CSS boxShadow und responsive Designmuster. Dokumentiert Bibliothekspräferenzen (expo-image für SF Symbols, expo-audio, expo-video,...
building-ui
expo
Vollständiger Leitfaden zum Erstellen schöner Apps mit Expo Router. Behandelt Grundlagen, Styling, Komponenten, Navigation, Animationen, Muster und native Tabs.
cicd-workflows
expo
Hilft beim Verstehen und Schreiben von EAS-Workflow-YAML-Dateien für Expo-Projekte. Verwenden Sie diese Fähigkeit, wenn der Benutzer nach CI/CD oder Workflows im Expo- oder EAS-Kontext fragt,…
data-fetching
expo
Verwenden beim Implementieren oder Debuggen von Netzwerkanfragen, API-Aufrufen oder Datenabrufen. Deckt fetch API, axios, React Query, SWR, Fehlerbehandlung, Caching ab…