What problem does it solve? Choosing and correctly implementing native UI components in Expo apps is error-prone: developers reach for community libraries like @gorhom/bottom-sheet or Reanimated when @expo/ui already provides native SwiftUI and Jetpack Compose equivalents, and platform-specific imports crash when used on the wrong OS. ## Core Features & Use Cases - Universal components first: Use Host, Column, Row, Button, Text, List, BottomSheet, Switch, Slider, Picker, Menu, and FieldGroup from a single API that runs on iOS, Android, and web (SDK 56+). - Drop-in replacements: Migrate off community libraries with API-compatible swaps under @expo/ui/community, covering bottom-sheet, datetimepicker, picker, slider, segmented-control, and more. - Platform-specific layers: Build @expo/ui/swift-ui or @expo/ui/jetpack-compose trees with modifiers, RNHostView, and useNativeState when universal components are insufficient, with correct .ios.tsx/.android.tsx file placement. - Use Case: When adding a bottom sheet to a map screen, use the universal BottomSheet with isPresented/onDismiss instead of installing @gorhom/bottom-sheet, and run the list-components script to confirm what the installed SDK version supports. ## Quick Start Ask the AI to add a native bottom sheet, picker, or settings-style list to your Expo screen using @expo/ui universal components.