Real SwiftUI,
written in React.
Apple’s views, modifiers and values as typed React components, rendered by SwiftUI itself.
npm installswiftui-react-native
Change it on the phone.
The binding follows.
Controls bind to state with useBinding. Flip a switch or drag the slider, and the value in your component updates with it.
const airplane = useBinding(false);const wifi = useBinding(true);const level = useBinding(0.62); <Form> <Toggle isOn={airplane}>Airplane Mode</Toggle> <Toggle isOn={wifi}>Wi-Fi</Toggle> <Slider value={level} in={[0, 1]} /></Form>Settings
Display & Brightness

+How it renders
Not a lookalike.
The real thing.
A <Toggle> isn’t drawn to look like iOS. Your component describes a SwiftUI view, Fabric gives it a place in your layout, and SwiftUI renders it.
You write React
Components and props mirror SwiftUI’s initializers. VStack(spacing: 12) becomes <VStack spacing={12}>.
Fabric lays it out
SwiftUI measures each view and hands the size to Fabric’s shadow tree, so Yoga places it alongside the rest of your React Native layout.
Settings
Display & Brightness

SwiftUI draws it
Each component runs inside a hosting controller as the real SwiftUI view, with system styling, accessibility and animation built in.
+How it’s built
Generated,
not wrapped.
Almost none of the API is written by hand. It’s generated from the SwiftUI that ships with Xcode, so when Apple adds an API, it shows up after the next generation.
Read from the SDK
Every public SwiftUI declaration is extracted from Xcode: views, modifiers, value types and where each one is available.
Turned into code
Each declaration becomes Swift, TypeScript and C++. Anything that doesn’t compile is left out, so what ships builds.
Modifiers keep their order
Chain them on compose(). They’re applied in sequence on the native side, exactly as they are in Swift.