How we sped up Android and iOS builds by 68% on CI
We made our engineers happier by cutting build times down from 50 minutes to 16.
Showing 20 of 23 articles (Page 1 of 2)
We made our engineers happier by cutting build times down from 50 minutes to 16.
At Pinterest, our mobile infrastructure is core to delivering a high-quality experience for our users. In this blog, I’ll showcase how the Pinterest Mobile Builds team is leveraging Honeycomb.
GitHub keeps mobile releases humming weekly with a tight process.
Meta shares how they cranked out Threads in just five wild months.
When Cash App was originally developed we had a single service powering all backend functionality, codenamed “Franklin”.
Premise uses Gradle Enterprise to catch Android build issues early.
Swiggy’s Gradle tool speeds up testing with incremental runs.
Zomato slashed Android build times by 95% with clever shortcuts.
Swiggy kicks off evolving mobile dev with Bitrise-powered wins.
Tokopedia sped up unit testing by 8x to save precious dev time.
Reddit sped up builds and cut grunt work so devs can focus on cool features.
Grab’s Project Bonsai spruces up their mobile dev process nicely.
Pinterest revamped their CI system, splitting tasks and streamlining to cut build times by over half.
LinkedIn uses a slick tool to speed up Android testing without hiccups.
Spotify juiced up their macOS CI, cutting iOS pre-merge checks by 75% with slick upgrades.
Pinterest found a single tweak that slashed their build times by a jaw-dropping 99%.
Gojek halved their Android build times to keep their developers moving fast.
Dropbox laid out a plan to bring their Android build system up to speed.
Dropbox put their Android build upgrade plan into action with grit.
Uber teamed up with JetBrains to figure out how Kotlin builds hold up when things get big and messy at scale.