Shipping Partiful on Autopilot
summary
Partiful ships a new Expo release every week for nearly three years and hits its 150th release this year by running a Friday 6:00 a.m. cron that triggers a daisy-chain GitHub Actions -> EAS build -> EAS submit to TestFlight and Google Play, uploads binaries to a GPT driver for AI end‑to‑end tests, and uses date-based versioning (eg 3.4.10 = April 10) so version conflicts vanish. Release conductors (now three rotating engineers) plus one QA approve builds and hotfixes flow through the same pipeline.
AI-written summary · about
chapters (11)
- 0:00Introduction to autopilot shipping
- 1:19What happens after 1.0
- 3:10From babysitter to team ownership
- 7:26Manual release pain points
- 10:21The dawn of autopilot
- 11:46Autopilot beyond CI/CD
- 14:33Date versioning freed us
- 15:34Human touch in autopilot
- 17:24Handling release issues
- 18:26Automated deadline for PRs
- 19:06Future improvements
related talks
29mOur Journey to Fully Automated Weekly Releases
12mExpo at scale in fast paced startup; Build, Deploy, Publish
28mHow to ship apps better, faster, stronger
22mExpo Application Services: Iterate with confidence
45mLet's automate one more thing
38mThe Power Of Process Automation
43mSecret Sauce of Cross-platform Mobile App Continuous Delivery
25mHow We Optimized Our Release Flow Using Google Play Console Release Tracks