A Simultaneous Release Crash Course
summary
Simultaneous release planning covers six concrete failure modes: missing localisations a week before launch, metadata rejections that add ~6 weeks, press-release timing or game‑breaking bugs costing 3–6 weeks, co‑publishing miscoordination adding 2–8 weeks, new platform certification delays of 1–2 months, and platforms changing launch timing unexpectedly. Solutions: use platform portals and certification kits, final metadata approved a month before launch, work backwards from the date, prepare release candidate 1 and safety builds, and document/duplicate responsibilities so two people can execute.
AI-written summary · about
chapters (16)
- 0:00A Crash Course in Simultaneous Releases
- 2:22Who The Heck is This Guy?
- 4:34Don't be a Dick
- 7:21Metadata Mistakes
- 14:29Press Release Problems
- 17:33Co-Publishing Cohesiveness
- 21:40New Platforms = New Problems
- 25:26Platforms take Priority
- 30:21Fail
- 31:32Work Backwards
- 38:14Safety Builds / Release Candidate 1
- 40:09Always Be Prepared
- 41:02Tell Two People
- 43:15Establish Priorities
- 45:07Gather the Infinity Stones
- 47:25Questions?
related talks
24mFuture-proofing your Android release process
21mFrom chaos to control: Future-proofing your Android release process
28mHow to ship apps better, faster, stronger
24mThe 7 Habits of Highly Effective Release Managers
06mIgnite: Escaping the Black Hole of Release Management
49mDeploying to production with confidence
43mSecret Sauce of Cross-platform Mobile App Continuous Delivery
38mFrom Development to Production: Tips to Optimise Android App Deployments