Expo React Native

Mobile prompts should name navigation patterns (tabs vs stack), safe areas, and platform differences you care about on day one. Orbit aims for component shapes that compile in Expo, but you must run simulators locally to catch native module gaps. Mention TypeScript strictness and styling approach (StyleSheet vs NativeWind).

Push notifications, deep links, and EAS build profiles are outside a UI scaffold—document them as follow-up tasks rather than expecting fully wired native services. Keep assets path conventions consistent so Metro resolves them.

Pair with web dashboards when your product is omnichannel; align design tokens conceptually even if implementations differ between React DOM and Native.

Snippet

import { View, Text } from 'react-native'
export function HomeScreen() {
  return (
    <View className="flex-1 p-4">
      <Text className="text-xl font-semibold">…</Text>
    </View>
  )
}