expo-ui

작성자: expo

프레임워크(오픈소스). @expo/ui 패키지로 네이티브 UI를 구축합니다: iOS에서는 실제 SwiftUI, Android에서는 Jetpack Compose를 React에서 렌더링하여 Expo 또는 React Native 앱에서 사용합니다. @expo/ui에서 가져온 범용 크로스 플랫폼 컴포넌트(Host, Column, Row, Button, Text, List 등), 인기 있는 React Native 커뮤니티 라이브러리(BottomSheet, DateTimePicker, Slider, Menu 등)의 드롭인 대체재, 그리고 플랫폼별 SwiftUI(@expo/ui/swift-ui, iOS 전용) 및 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.

expo의 다른 스킬

add-app-clip
expo
iOS App Clip 타겟을 Expo 앱에 추가합니다. 사용자가 App Clip, AASA, apple-app-site-association, appclips, 스마트 앱 배너를 언급하거나 출시를 원할 때 사용하세요.
android-e2e-testing
expo
Android 에뮬레이터에서 ADB를 사용하여 Expo Router 기능을 테스트합니다. 네이티브 Android 기능을 구현한 후 또는 Android에서 UI 동작을 확인할 때 사용하세요.
android-jetpack-compose
expo
Jetpack Compose로 Android UI를 구축하거나, remember/mutableStateOf로 상태를 관리하거나, 선언형 UI 패턴을 구현할 때 사용합니다.
api-routes
expo
Expo Router와 EAS Hosting에서 API 라우트를 생성하기 위한 가이드라인
building-native-ui
expo
네이티브 Expo 앱 구축을 위한 완벽 가이드로, 라우팅, 스타일링, 컴포넌트 및 플랫폼 규칙을 다룹니다. Expo Router 기초, 네이티브 탭, 스택 내비게이션, 모달, 폼 시트와 상세한 경로 구조 규칙을 포함합니다. Apple 휴먼 인터페이스 가이드라인에 맞춘 스타일링 규칙(플렉스박스 레이아웃, 세이프 에어리어 처리, 애니메이션, CSS boxShadow를 통한 그림자, 반응형 디자인 패턴)을 다루며, 라이브러리 선호도(expo-image의 SF Symbols, expo-audio, expo-video 등)를 문서화합니다.
building-ui
expo
Expo Router로 아름다운 앱을 구축하기 위한 완벽 가이드입니다. 기초, 스타일링, 컴포넌트, 내비게이션, 애니메이션, 패턴 및 네이티브 탭을 다룹니다.
cicd-workflows
expo
Expo 프로젝트의 EAS 워크플로 YAML 파일을 이해하고 작성하는 데 도움을 줍니다. 사용자가 Expo 또는 EAS 환경에서 CI/CD나 워크플로에 대해 질문할 때 이 스킬을 사용하세요.
data-fetching
expo
네트워크 요청, API 호출 또는 데이터 페칭을 구현하거나 디버깅할 때 사용합니다. fetch API, axios, React Query, SWR, 오류 처리, 캐싱 등을 다룹니다.