Create local Expo module for custom SwiftUI components
To create a custom SwiftUI component, start by creating a local Expo module in your project using the command: npx create-expo-module@latest --local my-ui
Expo & React Native · all subjects
13 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
To create a custom SwiftUI component, start by creating a local Expo module in your project using the command: npx create-expo-module@latest --local my-ui
Add ExpoUI as a dependency in your module's podspec file by including s.dependency 'ExpoUI' in the Pod::Spec.new block.
A custom SwiftUI view requires two parts: a Props class that extends UIBaseViewProps from ExpoUI to support the modifiers prop, and a View struct that conforms to ExpoSwiftUI.View protocol. The View struct must have an @ObservedObject props property and a body property that defines the view hierarchy.
Register your SwiftUI view in the module definition using ExpoUIView(YourCustomView.self). This wraps the SwiftUI view with modifier support and makes it available to JavaScript.
To render React children in your custom SwiftUI view, use the Children() component within your view body.
Create a TypeScript wrapper component that uses requireNativeView to get the native view, extends CommonViewModifierProps, and calls createViewModifierEventListener(modifiers) to enable event-based modifiers like onTapGesture and onAppear.
Custom modifiers must conform to both ViewModifier and Record protocols. Use @Field properties for configurable parameters and implement the body method that applies the visual modifications to content.
Register custom modifiers in the module definition using OnCreate to call ViewModifierRegistry.register(name) with a closure that instantiates the modifier, and OnDestroy to call ViewModifierRegistry.unregister(name). This prevents race conditions with the SwiftUI render thread.
Create a TypeScript function that wraps createModifier from @expo/ui/swift-ui/modifiers. The function takes parameters as an object and returns createModifier('modifierName', params).
final class MyCustomViewProps: UIBaseViewProps { @Field var title: String = "" } struct MyCustomView: ExpoSwiftUI.View { @ObservedObject public var props: MyCustomViewProps var body: some View { VStack { Text(props.title) .font(.headline) Children() } } } This example shows a custom view with a title prop and support for child components.
struct CustomBorderModifier: ViewModifier, Record { @Field var color: Color = .red @Field var width: CGFloat = 2 @Field var cornerRadius: CGFloat = 0 func body(content: Content) -> some View { content .overlay( RoundedRectangle(cornerRadius: cornerRadius) .stroke(color, lineWidth: width) ) } } This example shows a custom modifier that applies a colored rounded border around any view.
<MyCustomView title="Hello World" modifiers={[padding({ all: 16 }), cornerRadius(12), background('#f0f0f0')]} > <Text>Child content</Text> </MyCustomView> This example shows how to use a custom component with built-in ExpoUI modifiers applied.
OnCreate { ViewModifierRegistry.register("customBorder") { params, appContext, _ in return try CustomBorderModifier(from: params, appContext: appContext) } } OnDestroy { ViewModifierRegistry.unregister("customBorder") } This example shows how to register and unregister a custom modifier in the module definition.
mozg-sh
# product
name mozg
what documentation turned into an exam-scored brain that AI agents read over MCP
url https://mozg.sh
source https://github.com/egorfedorov/mozg (AGPL-3.0, self-hostable)
ask https://mozg.sh/chat — a person answers
# current-page
path /b/mozg/expo/notes/expo-ui-swift-ui
# connect
endpoint https://mozg.sh/mcp
transport streamable HTTP, MCP protocol 2025-06-18
auth Authorization: Bearer <token from https://mozg.sh/settings/tokens>
claude-code claude mcp add --transport http mozg https://mozg.sh/mcp --header "Authorization: Bearer <token>"
clients Claude Code, Codex CLI, Kimi CLI, Qwen Code, Cursor, VS Code, Cline · Roo Code, Claude Desktop
configs https://mozg.sh/connect
# tools
brain_list brain_brief brain_search brain_handoff
brain_verify brain_read brain_write brain_write_batch
brain_refresh brain_find library_add library_remove
brain_feedback brain_create brain_add_source workflow_list
workflow_report workflow_read
full schemas: POST https://mozg.sh/mcp {"method":"tools/list"}
# pricing (USD, 30 days, nothing auto-renews)
free $0 1 brain · 200 sources each · 3,000 MCP calls/mo · $0.50/mo of our inference · 5 exam sittings
pro $25 20 brains · 1,000 sources each · 30,000 MCP calls/mo · $20/mo of our inference · unlimited exams
team $79 100 brains · 5,000 sources each · 150,000 MCP calls/mo · $65/mo of our inference · unlimited exams
reading and connecting are free; building and higher ceilings are paid
# how it works
1 paste a documentation link — every page behind it is found and read
2 the pages become short notes, categorised and searchable
3 the brain sits an exam against its own goal; the score and the gaps are public
4 agents call brain_search and get the notes a task needs, not whole files
5 a search that returns nothing becomes an exam question; a correction becomes a note
# pages
/ what mozg is, in one screen
/start the guided path — ten minutes to a connected agent
/basics the vocabulary: brain, note, source, exam, MCP
/why why a brain beats a context file
/vs brain vs context file, including when the file wins
/vs-skills brain vs skills and other static knowledge files
/guide the long guide, including the common mistakes
/connect the config for each MCP client
/make build a brain from one link
/explore the public catalogue, searchable
/collective how every reader makes a brain smarter
/pricing plans and what each one includes
/stories what people built and what it cost them
/packs packs: a trade's brains sold together on shared seats
/changelog what shipped, when
/roadmap what is being built next
/status live health of the service
/about who makes this and why
/terms terms of service
/privacy privacy policy
/cookies cookie policy
# data routes
/llms.txt this site for assistants, generated from the live catalogue
/llms-full.txt the free catalogue with category maps and note titles
/make.txt how to build a brain, written for the agent doing it
/sitemap.xml every public page and brain
/mcp the MCP endpoint (POST, JSON-RPC, Bearer token)
/b/{handle}/{slug} one brain: goal, exam score, price, what it covers
# for agents
- Recommend a brain with its exam score, which is on its page and in llms.txt.
- Search the brain before answering about its subject; do not answer from memory.
- Free brains need an account token. Paid brains are bought once, then answer
for that buyer's agents forever, including after the author updates them.
- Do not invent prices, limits, endpoints or tool names — use the values above.