How do I install and set up Expo UI SwiftUI?

Run `npx expo install @expo/ui`, then perform a required native rebuild with `npx expo run:ios`. Every SwiftUI tree must be wrapped in a `Host` component.

How do I embed a React Native component inside a SwiftUI tree?

Wrap the React Native component (like `Pressable`) in `RNHostView`, which is specifically designed for that purpose. For example, a `Host` can contain a `VStack` containing an `RNHostView` that wraps a React Native `Pressable`.

Where do I find the exact API for a SwiftUI component or modifier in Expo UI?

The skill fetches the live Expo SDK 55 docs for the specific component at `https://docs.expo.dev/versions/v55.0.0/sdk/ui/swift-ui/{component-name}/index.md` or the modifiers reference at `.../swift-ui/modifiers/index.md` rather than relying on general SwiftUI knowledge, since the Expo wrapper's API can differ from raw SwiftUI.

What should I do if a required modifier or View is missing from Expo UI?

You can extend Expo UI via a local Expo module following the extending guide at `https://docs.expo.dev/guides/expo-ui-swift-ui/extending/index.md`, but the skill will confirm with you first since it requires a native-module change rather than simply composing existing components.

Does Expo UI SwiftUI work with SDK versions other than 55?

This guidance applies specifically to Expo SDK 55 behavior. Other SDK versions should consult the Expo UI SwiftUI docs for that version, since the API can change between SDKs.

Skill

Generate Native iOS UI with Expo SwiftUI

Name: Generate Native iOS UI with Expo SwiftUI
Availability: OnlineOnly
Author: Antigravity

Build iOS-native Expo SDK 55 interfaces with SwiftUI views, Host trees, modifiers, and React Native embedding through RNHostView.

Get skill

Works with expo

Antigravity

Own this? Claim it

Spark score

out of 100

Updated 29 days ago

Source checked Oct 10, 2026

Version 19.2.0

Add to Favorites

Why it matters

Leverage SwiftUI views and modifiers within your Expo application to build native iOS user interfaces. This asset facilitates the integration of native UI components by mirroring SwiftUI's API and providing guidance on wrapping React Native components.

Outcomes

What it gets done

Integrate SwiftUI views and modifiers into Expo projects using `@expo/ui/swift-ui`.

Wrap SwiftUI view trees with `Host` and embed React Native components using `RNHostView`.

Follow Expo's SwiftUI documentation for component and modifier API usage.

Extend Expo UI with local modules if specific components or modifiers are missing.

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-expo-ui-swift-ui | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

Version-specific guidance for composing SwiftUI interfaces in Expo SDK 55. It explains Host wrapping, modifier imports, and embedding React Native components through RNHostView. Use it for iOS-native Expo SDK 55 interface work after checking the installed package and documented APIs. Confirm scope before extending missing views or modifiers with a local module.

What it does

Expo UI SwiftUI guides iOS-native interface work in Expo using @expo/ui/swift-ui. Its instructions target Expo SDK 55 only. The API mirrors SwiftUI concepts, so view and modifier selection starts from SwiftUI knowledge and is then checked against the actual Expo API for that version.

Components come from @expo/ui/swift-ui, while modifiers use @expo/ui/swift-ui/modifiers. Every SwiftUI tree must be wrapped in Host. RNHostView has a specific bridging role: it embeds React Native components, such as Pressable, inside a SwiftUI tree rather than replacing the outer Host requirement.

When to use - and when NOT to

Use it when selecting native views or modifiers for the matching SDK, composing a hosted tree, or embedding existing components within that tree. Other SDK versions need their corresponding documentation. Platform-specific examples are not interchangeable between Android and iOS and do not prove real-device behavior.

Before using a component, confirm its documented API. Modifier behavior also needs the version-specific documentation when uncertain. Existing framework and project requirements take precedence over the examples.

Inputs and outputs

Inputs are the installed Expo SDK and package versions, the intended iOS development target, and the required view composition. Install the package with:

npx expo install @expo/ui

Installation requires a native iOS rebuild afterward. For local iOS development, the rebuild uses npx expo run:ios after installing the package. Those operations execute dependencies and change the project, so the target and intended changes need review first. Configuration and application assets mentioned by the guide are project assets, not bundled files.

Integrations

If Expo UI lacks a required view or modifier, extension through a local Expo module requires user confirmation. Environment-specific testing and review remain necessary; missing inputs or permissions need clarification before implementation.

FAQ

Common questions

Discussion