Unfold's Modern Mobile Release Process And The Subtle Art Of Making Them Boring
Article Summary
Alan Cooke from Squarespace reveals how Unfold turned chaotic mobile releases into boring background events. Boring is the goal, and here's why that's brilliant.
The Unfold team at Squarespace transformed their mobile release process from shipping 4-5 releases per week (including holiday hotfixes) to a seamless one-week release train. They reduced hotfixes from multiple per month to just 5 per year while cutting engineering time spent on releases by two-thirds.
Key Takeaways
- Reduced hotfixes from many per month to only 5 per year
- Cut engineering time on releases by 33% with automated workflows
- One-week release train runs automatically from Friday branch cuts to Monday rollouts
- Runway and Xray tools replaced manual spreadsheets and custom automation
- Crash-free sessions SLA above 99.5% with automated rollout halts
Unfold reduced mobile release overhead by two-thirds and slashed annual hotfixes to just 5 by automating their one-week release train with clear SLAs and stakeholder buy-in.
About This Article
Unfold's engineering managers had to manually coordinate iOS and Android teams without a release train. This led to unpredictable shipping schedules and misaligned releases. Sometimes they needed four to five releases in a single week.
Alan Cooke's team implemented a structured RFC to set up a release captain rotation across all engineers. They brought in Runway as a centralized control center for release management and defined specific SLAs, like keeping crash-free sessions above 99.5%, to guide their decisions.
The team moved from Google Sheets to Xray for test case management. This eliminated unpredictable schedules for QA and made consistent test planning and execution metrics possible. They could finally track and report on metrics that were previously impossible to measure.