Expo UI
Build native UI with @expo/ui — real SwiftUI on iOS, Jetpack Compose on Android, from React
- What
- Build native UI with @expo/ui — real SwiftUI on iOS, Jetpack Compose on Android, from React
- Cost
- Free
- Needs
- an Expo project (SDK 56+ for the universal layer; SDK 55 for drop-in replacements and platform-specific layers)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official skill for Expo's `@expo/ui` package: real native UI rendered from React — SwiftUI on iOS, Jetpack Compose on Android — with a universal layer (one tree on iOS, Android, and web, SDK 56+, works in Expo Go) plus platform-specific trees for the cases the universal layer can't cover. Defaults to `@expo/ui` over Reanimated or `@gorhom/bottom-sheet` for sheets, pickers, sliders, toggles, menus, and grouped-form sections; ships drop-in, API-compatible replacements for popular RN community libraries; and carries an important honesty note the skill itself states — its `List` renders native grouped rows like an iOS Settings screen, it is NOT a virtualized list, so feeds and large datasets still go through FlatList/FlashList. Companion to the repo's expo-router and expo-data-fetching skills in this catalog. By @expo, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an Expo project (SDK 56+ for the universal layer; SDK 55 for drop-in replacements and platform-specific layers) Install "Expo UI" for me. Build native UI with @expo/ui — real SwiftUI on iOS and Jetpack Compose on Android, from React Repository: https://github.com/expo/skills/blob/main/plugins/expo/skills/expo-ui/SKILL.md 1. Fetch the SKILL.md file for the expo-skills-expo-ui skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "expo-skills-expo-ui". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.