SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsreact-native-expo

react-native-expo

Frontend & websites

View repository

Updated 10-16 02:27

About this skill

React Native Expo

Targets Expo SDK 52–56, Expo Router v4, and EAS. For ecosystem libraries (state, Reanimated, React Navigation) see the react-native skill. For shadcn/ui-style components see the react-native-reusables skill.

Expo provides a full-stack toolchain on top of React Native: file-based routing via Expo Router, cloud build/deploy infrastructure via EAS, a native module authoring API, and a curated SDK of first-party libraries. This skill covers the Expo layer exclusively.

Core References

Topic Description Reference
Expo Router File-based routing, layouts, route groups, API routes, SDK 56 migration core-expo-router
EAS Overview EAS Build/Update/Submit/Deploy, eas.json structure, version management core-eas

Features

Topic Description Reference
EAS Build & Dev Client Build profiles, dev client setup, local builds, device installation features-eas-build
EAS Update & Deploy OTA updates, EAS Hosting, CI/CD YAML workflows features-eas-update-deploy
Expo Modules create-expo-module, module DSL, config plugins features-expo-modules
Upgrading Expo SDK Upgrade flow, cache clearing, SDK 53–56 breaking changes, module migrations features-upgrading

Best Practices

Topic Description Reference
Building UI Code style, expo-image, responsiveness, NativeTabs, navigation patterns best-practices-ui
Data Fetching fetch vs React Query, expo-secure-store, offline, env vars best-practices-data

Key Recommendations

  • Expo Go first — use npx expo start before building a dev client; custom builds are only needed for custom native code
  • EAS manages versions — set appVersionSource: "remote" in eas.json to avoid manual version bumps
  • File-based routing — routes live in app/; never co-locate components, types, or utilities in app/
  • API route secrets — use eas env:create for secrets; client-side env vars use EXPO_PUBLIC_ prefix (inlined at build time)
  • SDK upgrades — always run npx expo install --fix then npx expo-doctor after upgrading; clear caches before debugging