Plan a Release & Rollout Strategy

Background: Native [platform] app. Release type: [first launch / feature
update / risky change]. User base size: [if live]. I [do / don't] have
feature flags or remote config.

Use case: Plan a safe rollout so a bad build doesn't hit everyone at once,
since I can't instantly roll back a mobile release.

Implementation details:
- Staged/phased rollout: Play's staged percentage rollout and iOS's phased
  release—how to use each and what to watch during ramp
- The "you can't recall a binary" reality: feature flags / remote config
  to disable a broken feature without a new submission (a kill switch)
- Monitoring during rollout: crash-free rate and key metrics (ties to
  Section 12) with thresholds that halt the rollout
- Forcing/encouraging updates (minimum-version gating) for critical fixes
- A rollback plan: halt rollout, flag-off the feature, expedited review
  for a hotfix

Deliverable: A rollout plan with the phased-release steps per store, the
feature-flag/kill-switch strategy, the monitoring thresholds that pause or
halt the rollout, and the rollback/hotfix playbook.