react-native-expo-patterns

Guide React Native and Expo app configuration, deep linking, and EAS builds.

3|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/ai-enhanced-engineer/aiee-skills --skill react-native-expo-patterns-ai-enhanced-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: react-native-expo-patterns
Source: https://github.com/ai-enhanced-engineer/aiee-skills/tree/main/skills/react-native-expo-patterns
Command: npx skills add https://github.com/ai-enhanced-engineer/aiee-skills --skill react-native-expo-patterns-ai-enhanced-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses common challenges in managing and configuring React Native + Expo applications, improving efficiency and performance for developers.

Core Features & Use Cases

  • Managed vs. Bare Workflow: Provides guidance on choosing between managed and bare workflows, including setup time, native code access, and OTA updates.
  • SDK Migration: Offers insights into migrating from older SDK versions and common issues.
  • Expo Configuration: Walks through app.json configuration for both iOS and Android, including permissions, build numbers, and deep linking.
  • Expo Modules Integration: Details on integrating common Expo modules like Camera, FileSystem, and Sharing.
  • Deep Linking: Explains deep linking configuration and testing, ensuring seamless app navigation.
  • Font Loading: Describes techniques for loading fonts with splash screen coordination to improve app performance.
  • EAS Build Configuration: Covers EAS build workflow, including development, preview, and production builds.
  • OTA Updates: Guides on implementing OTA updates for JavaScript updates without app store approval.
  • Platform-Specific Code: Handles differences between iOS and Android development.
  • Troubleshooting: Provides solutions to common issues like build failures, camera permission issues, and deep linking not working.

Quick Start

To get started with this skill, read the 'Quick Start' section in the 'README.md' file within the 'skills/react-native-expo-patterns' directory.

Frequently Asked Questions about react-native-expo-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure deep linking in a React Native Expo app?

To configure deep linking in React Native Expo, you define the scheme and path mappings inside your app.json file. This setup ensures seamless app navigation and allows you to test deep links directly within your development workflow.

What is the best way to load custom fonts while coordinating the splash screen in Expo?

The best way to load custom fonts in Expo involves using the Font module and coordinating with the SplashScreen module. This technique prevents text flickering by ensuring fonts fully load before the splash screen hides, improving app performance.

Should I choose the managed or bare workflow for my React Native Expo project?

Choosing between managed and bare workflows depends on your native code access needs. The managed workflow offers faster setup and streamlined OTA updates, while the bare workflow provides direct access to native iOS and Android code when required.

How do I set up EAS builds for development, preview, and production environments?

Setting up EAS builds involves configuring the eas.json file to define separate build profiles for development, preview, and production. This workflow automates app compilation and generates binaries for each specific environment.

Can I push OTA updates to a React Native app without app store approval?

Yes, you can push OTA updates to ship JavaScript changes without app store approval. By implementing the Updates module, your app downloads and applies new JavaScript bundles automatically in the background.

Why does my Expo build fail when migrating to a newer SDK version?

Expo build failures during SDK migration often stem from incompatible native module versions or outdated dependencies. Troubleshooting involves aligning your package versions with the target SDK and clearing cache to resolve common migration issues.