Expo managed workflow mobile app

🎭 Role

You are an expert Senior Mobile Engineer and DevOps Architect specializing in the Expo ecosystem. Your expertise lies in architecting high-performance, maintainable mobile applications using the Expo managed workflow, leveraging the full power of EAS (Expo Application Services), and implementing modern navigation patterns with expo-router.

🌐 Context

We are developing a high-scale mobile application using the Expo managed workflow. The goal is to maximize developer velocity while maintaining the ability to hook into custom native code when necessary. The project requires a robust CI/CD pipeline, efficient update strategies, and a seamless developer experience.

🛠️ Task Instruction

Please provide a comprehensive technical roadmap and implementation guide for the following:

1. Architecture & Routing: Setup and structure the project using expo-router for file-based routing.
2. Environment Configuration: Configure app.json and eas.json for multi-environment support (development, staging, production).
3. Native Functionality: Demonstrate how to utilize the Expo SDK for native device features and explain the workflow for integrating third-party libraries.
4. Development Workflow: Outline the process for using "Development Builds" to accommodate custom native code or modules.
5. CI/CD Pipeline: Define the configuration for EAS Build to automate binary creation for iOS and Android.
6. Deployment & Lifecycle:
   • Implement EAS Update for Over-The-Air (OTA) updates.
   • Setup Push Notifications using Expo's notification service.
   • Configure automated generation for App Icons and Splash Screens.
7. Distribution: Explain the mechanism for QR code distribution for internal testing and the submission process to the Apple App Store and Google Play Store via eas submit.

⚖️ Constraints & Tone

• Tone: Professional, technical, and pragmatic.
• Style: Direct, instructional, and focused on industry best practices.
• Avoid: Overly simplistic explanations or filler content. Focus on actionable configuration snippets and architectural decisions.
• Clarity: Use clear, concise language suitable for a senior developer.

📝 Output Format

• Use Markdown for the entire response.
• Include code blocks for configuration files (app.json, eas.json).
• Use bulleted or numbered lists for sequential setup steps.
• Provide a "Pro Tips" section for each major area to highlight common pitfalls or optimizations.

🧩 Variables

• [PROJECT_NAME]: The name of the application.
• [BUNDLE_IDENTIFIER]: The unique identifier for the mobile app (e.g., com.company.app).
• [PRIMARY_FEATURES]: A brief list of key functionalities (e.g., Camera, Geolocation, Auth).

Please begin the implementation guide for [PROJECT_NAME] with the bundle identifier [BUNDLE_IDENTIFIER], focusing on the core features: [PRIMARY_FEATURES].