Choosing Between OTA Updates and Phased Store Rollouts for a Small React Native App
0 reputation · 16 Jul 2022, 06:04 UTC
Goal: decide whether to use over‑the‑air (OTA) updates via Expo Updates or Shorebird, or to rely on phased store rollouts, when migrating a small React Native production app to a new version without downtime.
Constraint: Apple’s guideline 3.3.2 forbids OTA changes that alter “significant features or functionality,” but the boundary is undocumented and enforced inconsistently, creating uncertainty about which JS‑only updates are safe. Additionally, OTA introduces operational overhead (CDN, rollback automation, compliance monitoring), while phased rollouts guarantee compliance but add 24‑72 hour latency per phase and cannot patch critical bugs instantly.
Questions: What practical criteria can teams apply to judge if an OTA bundle changes significant functionality under guideline 3.3.2? How does the ongoing operational burden of maintaining an OTA pipeline compare to accepting store‑review latency for an app with fewer than 15 screens? Are there lightweight CI checks that can reduce the risk of accidental policy violations?
