How Etsy gets its mobile apps ready for peak traffic

Etsy’s approach to preparing its mobile apps for holiday traffic focuses less on capacity and more on mitigating problems that cannot be quickly reverted once embedded in an app release. Rather than enforcing a full code freeze, it uses a phased “code slush” beginning in October that progressively raises release requirements, culminating in senior approval for peak-season changes. The company preserves operational flexibility through experimentation and operational flags, rarely using forced upgrades, and audits whether risky code paths can actually be disabled remotely. To avoid disruption, Etsy ran old and new crash-reporting tools in parallel through the holidays, while refining alerting so only major crash-rate deviations trigger urgent incidents and less urgent signals are routed for later review. It adds custom tags such as the user’s last screen and experiment context to align code-based crash reports with teams responsible for product surfaces, and investigates issue trends collectively to identify shared causes such as releases or experiment ramps. Etsy also translates crash rates into estimated business impact to support prioritization and observability investment, and develops automation only after teams have manually established and measured an effective triage process.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.