Android × CI/CD
Android CI/CD
We track 33 Android CI/CD case studies from 26 engineering teams. Walmart, Pinterest and Shopify write about it most. Many posts also cover Testing and Build Time. The posts run from 2016 to 2026. The newest is from September 2026.
Android CI/CD articles 1–30 of 33
How We Built a Virtual Device Farm for Android E2E Tests
İbrahim Süren from Trendyol reveals how they ditched job-local emulators and built their own virtual device farm. The result? Predictable Android E2E tests at scale without the resource contention nightmares.
How AI Learned to Investigate Mobile Build Failures Like an Experienced Support Engineer
Archana Indran's team at Salesforce turned years of mobile debugging expertise into AI that investigates build failures like a senior engineer. Eight people now support 60+ repositories with less firefighting.
Tuning Android build nodes for maximum throughput
Wealthfront's Android team cut their CI build times by rethinking how Gradle uses resources on AWS EC2 instances. Turns out, more workers doesn't always mean faster builds.
Flutter vs .NET MAUI in 2026: Architecture, Tooling, CI/CD, and Migration Trade-offs
The article content appears to be just a promotional snippet for Shorebird's integration tool, not the full Flutter vs .NET MAUI comparison promised in the title. Without the actual article content, I cannot pr...
Maestro at Scale: Architecting a Deterministic Mobile Test Platform
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...
Supercharging Mobile Development with Permanent Work Trees and Claude
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.
Delivering Mobile App Updates Faster
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.
Our Buildkite Brings All the Devs to the Yard: (Re)Building Reddit Mobile CI in 2025
Reddit's mobile team had zero professional CI experience. Then they cut build times in half and transformed developer happiness.
Optimizing CI/CD Efficiency with Git Hooks
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...
Keeping Up with Android App Size Growth
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?
How We Improved Testing Processes Using Ephemeral Environment
Swiggy was missing production deadlines because their UAT environments were constantly unstable or unavailable. Sound familiar?
Building a Multi-Pipeline CI Setup for Running Automated Tests in GitLab
Gojek's engineering team cracked a common CI/CD headache: how do you run automated tests from a separate repo without creating pipeline chaos?
Mobile Developer Experience at Slack
Slack's 8-person Mobile DevXp team saved $240K annually just by improving PR notifications. Most companies are massively underinvesting in developer experience.
Improving the CI/CD pipeline for mobile app development
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.
Mobile DevOps Journey: Evolving Mobile Development at Swiggy (Episode 1)
Swiggy's mobile team was drowning in Jenkins bottlenecks. Build times were slow, machines crashed frequently, and manual interventions killed velocity.
How we ship GitHub Mobile every week
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.
Improving Product Reliability by Imposing Constraints as a Part of CI/CD Process
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.
ACF Automated Code Formation Engineering Excellence
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.
Automating Integration Tests To Ensure Android App Quality
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...
How Pinterest Leverages Honeycomb to Enhance CI Observability and Improve CI Build Stability
Pinterest sends 1 million CI build events to Honeycomb daily. Here's how they turned that data into a competitive advantage for mobile development.
Speeding Up Android Unit Tests with Test Sharding on GitLab CI
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.
Improve Reliability with Observability Tracing in Your CI/CD Pipeline
Walmart's engineering team reveals how observability tracing transformed their CI/CD pipeline reliability. The secret? Treating data requests like package tracking.
How We Designed Our Continuous Integration System to Be More Than 50% Faster
Pinterest's Engineering Productivity team slashed CI build times by over 50% in one week. Here's the architecture that made it possible.
Revamping the Android Testing Pipeline at Dropbox
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.
5 Minute DevOps Effective Testing
Walmart's DevOps team has a bold claim: if you're not testing during development, you're risking the business. Here's why your testing strategy might be fundamentally broken.
Better Android Testing at Airbnb (Part 6)
Airbnb's Android tests take 2 hours to run but finish in minutes. Here's the CI infrastructure that makes it possible.
Targeted Code Coverage Reports For Android Continuous Builds
Brian Terczynski from Thumbtack reveals how their Android team solved a critical problem: developers couldn't see which specific lines in their code changes lacked test coverage. The solution? Two custom report...
Running Android Instrumentation Tests on Circle CI Without a Third Party Service
Doğu Deniz Uğur challenges CircleCI's own documentation. While the official docs say Android emulator tests aren't supported on their Linux VMs, he found a workaround that eliminates the need for Firebase Test ...
Mobile Tophatting at Shopify
Pedro Piñera from Shopify reveals how they turned a 15-minute context switch into a single command. No QA team? No problem when developers can test each other's work this fast.
Automating Mobile App Localization
Dmytro Khmelenko reveals how Freeletics turned localization from a bottleneck into a fully automated pipeline. The results? Measurable revenue spikes in newly localized markets and zero manual translation work.