EAS Updates for Seafarers
summary
Kadmos uses EAS updates plus Expo GitHub Actions fingerprinting to decide when JavaScript-only changes can ship over the air instead of a full store release, turning a ~35MB Play Store bundle into roughly 35 megabytes downloaded from stores vs a ~4MB OTA payload in the demo. A custom version service validates stores, marks releases optional or mandatory, integrates TestFlight/Play/Huawei, and the pipeline demonstrably reduces monthly data usage for seafarers with 500MB caps.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 2:34The CMOS mission
- 4:01User context and challenges
- 6:12Technical strategies
- 8:01Pipeline and versioning
- 10:56Demo: Over-the-air updates
- 14:01Data efficiency case study
- 17:03Summary and takeaways
- 19:49Future outlook
related talks
22mExpo Application Services: Iterate with confidence
12mExpo at scale in fast paced startup; Build, Deploy, Publish
21mShipping Partiful on Autopilot
20mPublish Updates with Expo and React Native
20mBuilding a Mobile App with Expo, EAS and React Native
18mWhat is your app actually doing in production?
25mNot your grandparents’
25mLimitless App Development with Expo and React Native