staged-rollouts
Installation
SKILL.md
Staged Rollouts
Instructions
Never ship a new mobile version to 100% of users at once. The point of a staged rollout is to catch the regressions your QA missed before they become a one-star-review avalanche or a rollback that you cannot execute (you cannot force users to downgrade).
1. Why Staged
- No instant rollback. A bad mobile build stays installed. Only new installs can receive a fix. Staging buys time.
- Heterogeneity. OS versions, device models, locales, carriers. Staged cohorts sample this variance.
- SDK surprises. New or updated SDKs can crash in production configurations you did not anticipate.
- Store review latency. A hotfix can take hours to days. Staged exposure is your primary safety net.