What problem does it solve? Shipping an Expo app involves juggling EAS build profiles, store credentials, TestFlight submissions, web deploys, and OTA update monitoring. This Skill consolidates the commands, configurations, and platform-specific guides needed to release and operate Expo apps without hunting through documentation. ## Core Features & Use Cases - Store Submission: Build and submit iOS and Android production binaries to the App Store and Google Play with eas build and eas submit, including credential and service account setup. - TestFlight & Dev Clients: Distribute beta builds via npx testflight and create development clients for testing custom native code on physical devices. - Web & API Hosting: Deploy Expo Router web apps and +api.ts API routes to EAS Hosting (Cloudflare Workers runtime) with PR previews. - OTA Update Monitoring: Query crash rates, adoption, and embedded-vs-OTA user splits with eas update:insights and eas channel:insights. - Use Case: After merging a release branch, run a production build for both platforms, submit to TestFlight and the Play internal track, then monitor the OTA rollout's crash rate before promoting to production. ## Quick Start Ask the assistant to build and submit your Expo app to TestFlight using EAS with a production profile.