Explore 15 articles from Slack on mobile performance
Showing 15 of 15 articles (Page 1 of 1)
Slack's Android team tackled a VPAT accessibility audit and found critical gaps that affected screen reader users. Here's what they fixed and why it matters for your mobile app.
Slack's mobile team faces a unique challenge: users expect desktop-level performance while bouncing between subway tunnels and spotty cellular networks.
Slack's 8-person Mobile DevXp team saved $240K annually just by improving PR notifications. Most companies are massively underinvesting in developer experience.
Slack just wrapped a massive mobile refactor. The results? 68% of iOS and 92% of Android codebases modernized, with CI times slashed by over 60%.
Slack's mobile codebase was slowing teams down. Their solution? Break the monolith into hundreds of independent modules.
Slack's engineering team ran into a classic performance testing problem: spinning up load tests was so time-consuming that teams avoided doing it. Their solution? Never stop testing.
Tracy Stampfli and Bryan Stern reveal how Slack's mobile teams tackled crippling tech debt that was actively slowing product roadmaps. Their solution? A bold 6-month stabilization sprint that transformed both i...
Mathias Roth from Slack reveals how a hardcoded Android display name prefix saved their Conversation Bubbles implementation. What started as straightforward API work turned into a detective story involving work...
"My app is slow" - every engineer's nightmare. Slack's mobile team was tired of hitting dead ends when debugging performance issues.
Slack processes 8.5 billion spans daily, but their tracing system looks nothing like traditional distributed tracing. Here's why they rebuilt it from scratch.
Slack cut load times by 65% for large teams by doing less work, not more. Their secret? Strategic laziness.
Slack's desktop client was grinding to a halt as teams scaled. The culprit? An over-reliance on browser LocalStorage that seemed smart at first.
Kevin, a Staff Engineer at Slack, shares how a distributed mobile team ships features across Vancouver and San Francisco without stepping on each other's toes. His secret? Strategic work separation and dogfoodi...
Slack's engineering team faced a classic scale problem: three platforms, three definitions of 'app launch,' and zero ability to compare performance meaningfully.
Slack was making 4.2 million users wait through loading screens every single day. Time to fix that.