Phase 9Days 48-52

Production Delivery & Operations

EAS Build, credentials, signing, channels, updates, stores, observability, rollout, and incident response

Phase Goal

Ship repeatable signed releases and operate them safely after users install them.

Progress

Day 48: EAS Build, Credentials & Environments

Day 49: EAS Update, Runtime Versions & Rollback

Day 50: Store Submission & Release Engineering

Day 51: Observability, Crashes & Product Signals

Day 52: Mini Project — Indie Cinema Release Train

Capstone
Indie Cinema Release Train

Take a supplied local cinema programme app from reproducible build profiles to a review-ready release. Prove that a schedule-text update can roll forward and back safely, while a native notification capability change is held for a new binary.

  • EAS development, preview, and production profiles with credential, secret, version, and environment boundaries
  • Update channels, runtime compatibility decision, phased rollout, rollback drill, and binary-required change record
  • Symbolicated intentional crash, startup/network trace, privacy-safe SLOs, store metadata, accessibility notes, and incident runbook
  • Transfer: respond to a bad update that crashes only on one runtime version without disrupting unaffected installs

Phase Complete!

After this phase, you'll be able to:

  • Native binary versus JavaScript bundle artifacts
  • Development, preview, and production profiles
  • Android signing and iOS certificates/profiles mental model
  • Secrets, environment variables, and reproducible builds
  • Compatible native runtime versus update bundle
  • Channels, branches, runtimeVersion, and rollout policy
  • Update startup behavior, monitoring, and rollback
  • When an app-store binary is mandatory

You can apply Phase 9 skills in a tested mobile project on Android and iOS.