29 articles on CI/CD for iOS performance
Showing 20 of 29 articles (Page 1 of 2)
Emre Erkek from Getir reveals how they turned Maestro from a simple testing tool into a deterministic platform that runs thousands of tests daily. Most teams fail at E2E testing scale—here's the architecture th...
Manoj Kumar Gubba from Mercari's iOS team reveals how they ship mobile updates in just 3-7 days. Most teams take 1-2 weeks, but Mercari's approach cuts that in half while maintaining stability.
Reddit's mobile team had zero professional CI experience. Then they cut build times in half and transformed developer happiness.
Illia Kucheriavyi from Revolut reveals how 120+ iOS engineers ship weekly releases across 5 apps while maintaining 150,000+ automated tests. Their secret? A mono-repo with 160 shared modules and build times tha...
Alberto De Bortoli from Just Eat Takeaway reveals how his team built a fully automated iOS CI system that supports 40+ developers with just 5 bare metal instances. No manual SSH. No weekend waste. Pure infrastr...
Bevan Christian from IDN Engineering cut iOS CI/CD time by 76.85% with one platform switch. Here's how a simple migration delivered results most teams only dream about.
Swiggy was missing production deadlines because their UAT environments were constantly unstable or unavailable. Sound familiar?
Gojek's engineering team cracked a common CI/CD headache: how do you run automated tests from a separate repo without creating pipeline chaos?
Slack's 8-person Mobile DevXp team saved $240K annually just by improving PR notifications. Most companies are massively underinvesting in developer experience.
Johnson Li from Coupang reveals how migrating from Mac minis to AWS EC2 transformed their mobile CI/CD pipeline. Their team was drowning in 3,000+ daily builds with 1-hour wait times.
Swiggy's iOS team slashed build wait times by 80% and cut 8-10 minutes off every build. Here's the detailed playbook they used with Bitrise.
Swiggy's mobile team was drowning in Jenkins bottlenecks. Build times were slow, machines crashed frequently, and manual interventions killed velocity.
Pierre Abi-aad from leboncoin took Xcode Cloud for a test drive with a 28-developer iOS team. His verdict? Not ready for complex architectures, but Apple's onto something.
GitHub Mobile ships to production every single week with a tiny team. Their secret? Ruthless automation that turns a multi-day release process into a Saturday morning workflow.
Jimmy Harijanto from Blibli.com shows how to stop manually building iOS releases in Xcode. His team automated the entire pipeline from code commit to TestFlight using open-source tools.
Revolut built a system that automatically blocks code deployments based on security risk and bug count. Here's how they shifted security left without slowing down 165,000+ pull requests.
Walmart's engineering team cut time-to-market for cloud self-service platforms from 26 weeks to under 2 weeks. Here's the framework that made it possible.
Alexander Kulabukhov from Bumble Tech reveals the hidden costs of iOS modularization that nobody warns you about. Spoiler: visualizing 50+ module dependencies looks like a tangled mess, and your CI will cry for...
Alberto De Bortoli from Just Eat Takeaway reveals how they slashed their iOS CI complexity by consolidating dozens of module repos into one. The result? One PR instead of multiple, faster iteration, and smarter...
Pinterest sends 1 million CI build events to Honeycomb daily. Here's how they turned that data into a competitive advantage for mobile development.