Native UI with Expo Router

Patterns and conventions for building native mobile applications with Expo Router and React Native.

References

Consult these as needed:

• - ./references/route-structure.md — Route conventions, dynamic routes, groups, folder organization
• INLINECODE1 — Native tab bar with NativeTabs, iOS 26 features
• INLINECODE2 — SF Symbols with expo-symbols, icon names, animations, weights
• INLINECODE3 — Native iOS controls: Switch, Slider, SegmentedControl, DateTimePicker
• INLINECODE4 — Blur effects (expo-blur) and liquid glass (expo-glass-effect)
• INLINECODE5 — Reanimated: entering, exiting, layout, scroll-driven, gestures
• INLINECODE6 — Search bar with headers, useSearch hook, filtering patterns
• INLINECODE7 — CSS gradients via experimental_backgroundImage (New Architecture only)
• INLINECODE8 — Camera, audio, video, file saving
• INLINECODE9 — SQLite, AsyncStorage, SecureStore
• INLINECODE10 — 3D graphics and GPU visualizations with WebGPU/Three.js
• INLINECODE11 — Stack headers and toolbar with buttons, menus, search bars (iOS)
• INLINECODE12 — Form sheet presentation patterns

Running the App

Always try Expo Go first before creating custom builds.

1. 1. Start with npx expo start and scan the QR code
2. Test features in Expo Go
3. Only create custom builds when required

When Custom Builds Are Required

Use npx expo run:ios/android or eas build only for:

• - Local Expo modules (custom native code in modules/)
• Apple targets (widgets, app clips via @bacons/apple-targets)
• Third-party native modules not in Expo Go
• Custom native configuration beyond INLINECODE18

Expo Go supports all expo-* packages, Expo Router, Reanimated, Gesture Handler, push notifications, and deep links out of the box.

Installation

OpenClaw / Moltbot / Clawbot

CODEBLOCK0

Code Style

• - Escape nested backticks and quotes correctly
• Always use import statements at the top of the file
• Use kebab-case for file names: INLINECODE20
• Remove old route files when restructuring navigation
• No special characters in file names
• Configure tsconfig.json path aliases; prefer aliases over relative imports

Routes

See ./references/route-structure.md for detailed conventions.

• - Routes belong in the app directory
• Never co-locate components, types, or utilities in app/ — this is an anti-pattern
• Always have a route matching /, possibly inside a group route

Library Preferences

Never use deprecated modules: Picker, WebView, SafeAreaView, AsyncStorage (from RN core), or legacy expo-permissions.

Responsiveness

• - Wrap root components in a scroll view
• Use <ScrollView contentInsetAdjustmentBehavior="automatic" /> instead of INLINECODE42
• Apply contentInsetAdjustmentBehavior="automatic" to FlatList and SectionList too
• Use flexbox instead of Dimensions API
• Prefer useWindowDimensions over Dimensions.get() for screen measurement

Behavior

• - Use expo-haptics conditionally on iOS for delightful interactions
• Use views with built-in haptics (<Switch />, @react-native-community/datetimepicker)
• First child of a Stack route should almost always be a ScrollView with INLINECODE49
• Prefer headerSearchBarOptions in Stack.Screen options for search bars
• Use <Text selectable /> on data that users may want to copy
• Format large numbers: 1.4M, 38k
• Never use intrinsic elements (img, div) outside webviews or Expo DOM components

Styling

Follow Apple Human Interface Guidelines.

General Rules

• - Prefer flex gap over margin and padding
• Prefer padding over margin
• Always account for safe area via stack headers, tabs, or INLINECODE54
• Ensure both top and bottom safe area insets are handled
• Inline styles preferred over StyleSheet.create unless reusing styles
• Add entering/exiting animations for state changes
• Use { borderCurve: 'continuous' } for rounded corners (not capsule shapes)
• Use navigation stack title instead of custom text headers
• On ScrollView, use contentContainerStyle for padding/gap (avoids clipping)
• CSS and Tailwind are not supported — use inline styles

Text Styling

• - Add selectable prop to <Text/> elements showing important data or errors
• Use { fontVariant: 'tabular-nums' } on counters for alignment

Shadows

Use CSS boxShadow style prop. Never use legacy RN shadow or elevation styles.

CODEBLOCK1

Inset shadows are supported.

Navigation

Link

Use <Link href="/path" /> from expo-router for navigation.

CODEBLOCK2

Include <Link.Preview> whenever possible to follow iOS conventions. Add context menus and previews frequently.

Stack

• - Always use _layout.tsx files to define stacks
• Use Stack from expo-router/stack for native navigation stacks
• Set page titles in Stack.Screen options: INLINECODE68

Context Menus

Add long-press context menus to Link components:

CODEBLOCK3

Link Previews

CODEBLOCK4

Can be combined with context menus.

Modal

Present a screen as a modal:

CODEBLOCK5

Prefer this over custom modal components.

Sheet

Present as a dynamic form sheet:

CODEBLOCK6

INLINECODE69 enables liquid glass on iOS 26+.

Common Route Structure

Standard app layout with tabs and stacks:

CODEBLOCK7

Root layout:

CODEBLOCK8

Shared group layout:

CODEBLOCK9