<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/ZBHC1DeUU" -->

---
title: Inside SWSH's automated mobile release pipeline with...
description: SWSH, a social photo-sharing app built on a single React Native codebase, ships native releases to iOS, an iOS App Clip, and Android roughly once a week, and...
canonical: https://daily.dev/posts/inside-swsh-s-automated-mobile-release-pipeline-with-expo-expo-blog-zbhc1deuu
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Inside SWSH's automated mobile release pipeline with Expo — Expo blog | daily.dev
og:description: SWSH, a social photo-sharing app built on a single React Native codebase, ships native releases to iOS, an iOS App Clip, and Android roughly once a week, and...
og:url: https://daily.dev/posts/inside-swsh-s-automated-mobile-release-pipeline-with-expo-expo-blog-zbhc1deuu
og:image: https://api.daily.dev/og/posts/ZBHC1DeUU.png
og:image:alt: Inside SWSH's automated mobile release pipeline with Expo — Expo blog
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Inside SWSH's automated mobile release pipeline with Expo — Expo blog

**[Expo Blog](https://daily.dev/sources/expo-blog)** · 6 min read · 5 upvotes · 0 comments

## Summary

SWSH, a social photo-sharing app built on a single React Native codebase, ships native releases to iOS, an iOS App Clip, and Android roughly once a week, and runs about 300 builds a month using Expo's EAS toolchain. The team runs EAS Build locally on self-hosted macOS and Android runners for cost reasons at their volume, keeps signing credentials entirely inside EAS so CI only ever holds a single Expo access token, and uses EAS Submit alongside a custom App Store Connect API pipeline to handle App Store versioning, metadata, and App Clip configuration. Every release, including JavaScript-only EAS Update pushes, is validated by an in-house Appium/WebDriverIO/Vitest end-to-end suite called Meridian that exercises login, sign-up, upload, and deep linking across simulators and emulators. EAS Observe then tracks production performance metrics like time-to-interactive to catch regressions after release.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://expo.dev/blog/inside-swsh-automated-mobile-release-pipeline-with-expo>

## Questions this post answers

### How can I run EAS Build on my own hardware instead of Expo's cloud builds?

EAS supports local builds through the eas build command with a local flag, using the same build tooling that runs in Expo's cloud. This lets a team keep EAS's orchestration, credential management, and submission while moving the actual compilation onto self-hosted macOS and Android runners, which is worthwhile at high build volumes like 300 builds a month.

_Teams weighing local versus cloud EAS builds can follow real-world release pipeline breakdowns on daily.dev._

### How do I automate App Store Connect submissions including App Clip metadata?

Beyond EAS Submit, which pushes builds to Google Play and App Store Connect, iOS App Clip configuration requires a custom pipeline that calls the App Store Connect API directly: polling for the processed build, creating the App Store version, setting metadata and release notes, configuring the App Clip's default experience including card subtitle and image, and submitting for review.

_Developers automating App Clip and store submissions can find similar release engineering writeups on daily.dev._

### What is EAS Metadata and when should I use it instead of a custom App Store Connect pipeline?

EAS Metadata is Expo's declarative solution for managing App Store metadata, and most teams should use it rather than building a custom pipeline. A custom App Store Connect API pipeline is only worth building for edge cases like configuring App Clip experiences, which one team built in-house because their App Clip needs went beyond what EAS Metadata covers.

_Anyone deciding between EAS Metadata and a custom submission pipeline can compare real approaches on daily.dev._

## Similar posts on daily.dev

- [How Posh went from manual weekly mobile releases to continuous delivery with Expo](https://daily.dev/posts/how-posh-went-from-manual-weekly-mobile-releases-to-continuous-delivery-with-expo-spwvniuaf) · Expo Blog · 4 upvotes · 0 comments
- [EAS Cloud iPhones, Automated Screenshot Pipelines, and Nuking Every Simulator You Ever Loved](https://daily.dev/posts/eas-cloud-iphones-automated-screenshot-pipelines-and-nuking-every-simulator-you-ever-loved-gfubtxcjz) · ITNEXT · 0 upvotes · 0 comments
- [Agentic CI for Expo apps with TesterArmy — Expo blog](https://daily.dev/posts/agentic-ci-for-expo-apps-with-testerarmy-expo-blog-d5nssouhz) · Expo Blog · 0 upvotes · 0 comments
- [How we rebuilt the Shopify app in 12 weeks \(2026\)](https://daily.dev/posts/how-we-rebuilt-the-shopify-app-in-12-weeks-2026--opgx3l51s) · RUBYLAND · 1 upvotes · 0 comments

---

Tags: [#testing](https://daily.dev/tags/testing), [#mobile](https://daily.dev/tags/mobile), [#cicd](https://daily.dev/tags/cicd), [#react-native](https://daily.dev/tags/react-native)

[View this post on daily.dev](https://daily.dev/posts/inside-swsh-s-automated-mobile-release-pipeline-with-expo-expo-blog-zbhc1deuu)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Inside SWSH's automated mobile release pipeline with Expo — Expo blog","url":"https://daily.dev/posts/inside-swsh-s-automated-mobile-release-pipeline-with-expo-expo-blog-zbhc1deuu","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/inside-swsh-s-automated-mobile-release-pipeline-with-expo-expo-blog-zbhc1deuu"},"datePublished":"2026-08-26T13:58:54.405Z","dateModified":"2026-09-14T09:22:17.425Z","description":"SWSH, a social photo-sharing app built on a single React Native codebase, ships native releases to iOS, an iOS App Clip, and Android roughly once a week, and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3df736cb89152f2b67c66d067a1498d5?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3df736cb89152f2b67c66d067a1498d5?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Expo Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Expo Blog","logo":"https://media.daily.dev/image/upload/s--E7LK6L3y--/f_auto,q_auto/v1774179051/logos/expo-blog?_a=BAMAMiWQ0","url":"https://daily.dev/sources/expo-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/inside-swsh-s-automated-mobile-release-pipeline-with-expo-expo-blog-zbhc1deuu","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,mobile,cicd,react-native","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Expo Blog","item":"https://daily.dev/sources/expo-blog"},{"@type":"ListItem","position":3,"name":"Inside SWSH's automated mobile release pipeline with Expo — Expo blog"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/inside-swsh-s-automated-mobile-release-pipeline-with-expo-expo-blog-zbhc1deuu#faq","mainEntity":[{"@type":"Question","name":"How can I run EAS Build on my own hardware instead of Expo's cloud builds?","acceptedAnswer":{"@type":"Answer","text":"EAS supports local builds through the eas build command with a local flag, using the same build tooling that runs in Expo's cloud. This lets a team keep EAS's orchestration, credential management, and submission while moving the actual compilation onto self-hosted macOS and Android runners, which is worthwhile at high build volumes like 300 builds a month. Teams weighing local versus cloud EAS builds can follow real-world release pipeline breakdowns on daily.dev."}},{"@type":"Question","name":"How do I automate App Store Connect submissions including App Clip metadata?","acceptedAnswer":{"@type":"Answer","text":"Beyond EAS Submit, which pushes builds to Google Play and App Store Connect, iOS App Clip configuration requires a custom pipeline that calls the App Store Connect API directly: polling for the processed build, creating the App Store version, setting metadata and release notes, configuring the App Clip's default experience including card subtitle and image, and submitting for review. Developers automating App Clip and store submissions can find similar release engineering writeups on daily.dev."}},{"@type":"Question","name":"What is EAS Metadata and when should I use it instead of a custom App Store Connect pipeline?","acceptedAnswer":{"@type":"Answer","text":"EAS Metadata is Expo's declarative solution for managing App Store metadata, and most teams should use it rather than building a custom pipeline. A custom App Store Connect API pipeline is only worth building for edge cases like configuring App Clip experiences, which one team built in-house because their App Clip needs went beyond what EAS Metadata covers. Anyone deciding between EAS Metadata and a custom submission pipeline can compare real approaches on daily.dev."}}]}
```

