Expo SDK 50 Managed Workflow EAS Pricing Change for Low-Traffic Apps
0 reputation · 25 Mar 2023, 18:20 UTC
Expo SDK 50 Managed Workflow EAS Pricing Change for Low-Traffic Apps
The goal is to lower operating expenses for a low-traffic Expo managed-workflow app while preserving support for occasional updates. Expo SDK 50 introduced EAS Build pricing tied to build minutes and device count, which can dominate costs when builds run frequently. The managed workflow also keeps the `expo start` dev server active by default, consuming compute even during idle periods.
Constraints include variable EAS pricing tiers, shifting free quotas, and scattered cost documentation that requires current verification. It is unclear whether bundle size or runtime dependencies from the managed workflow affect low-traffic performance enough to change the decision.
Can build minutes be reduced for infrequent updates without disabling necessary cloud builds? Can the dev server be disabled or limited to lower hidden compute costs? Is `expo export` a viable lower-cost path to standalone binaries for low-traffic workloads?
expo