29 articles on CI/CD for Android 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...
Umair Ali from ZAR Engineering turned weeks of mobile development work into single days by eliminating a hidden productivity killer. The secret? Rethinking how Git worktrees interact with AI coding assistants.
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.
Bevan Christian from IDN Engineering breaks down a CI/CD cost problem most teams ignore: GitHub Actions bills can hit $1,440/month for a 10-person team doing basic PR testing. His solution? Move testing local w...
Square manages hundreds of mobile engineers in a monorepo, all contributing to apps that must stay under Google Play's 150 MB limit. How do they prevent app bloat at scale?
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 mobile team was drowning in Jenkins bottlenecks. Build times were slow, machines crashed frequently, and manual interventions killed velocity.
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.
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.
Brian Terczynski from Thumbtack reveals how his team eliminated weekly manual QA sessions that were draining engineering time. Their solution? A fully automated integration testing pipeline that catches bugs be...
Pinterest sends 1 million CI build events to Honeycomb daily. Here's how they turned that data into a competitive advantage for mobile development.
Walmart's engineering team reveals how observability tracing transformed their CI/CD pipeline reliability. The secret? Treating data requests like package tracking.
Fadel Trivandi Dipantara from Bukalapak faced a brutal reality: 3,000+ test classes taking 2.5 hours to run. His team couldn't ship fast enough, and traditional solutions kept failing.
Pinterest's Engineering Productivity team slashed CI build times by over 50% in one week. Here's the architecture that made it possible.
Dropbox cut their Android CI pipeline from 75 minutes to 25 minutes without switching build systems. Here's how a team of 60+ mobile engineers solved testing at scale.