Systems | Development | Analytics | API | Testing

‍Mobile development has a reputation for being slow, complex, and harder than it needs to be. Platform quirks, rigid review gates, and ever-growing app complexity can make it feel like the toolchain is working against you. But the data tells a different story. We analyzed tens of millions of builds across thousands of mobile teams on Bitrise, spanning three years of real-world data from 2022 to 2025. The results challenge some common assumptions, and confirm others.

For fifty years, the hardest part of software was writing it. That's no longer true. In 2025, AI coding assistants went mainstream — 90% of developers now use them (DORA 2025). Then came background agents: autonomous systems that take a ticket, write the code, run the tests, and open a pull request while the engineer sleeps. Stripe merges over 1,000 AI-written PRs per week. Ramp reached 30% AI-authored PRs within two months. Spotify has merged 1,500+ agent-generated PRs into production.

For small enterprises with big ambitions, Tapcart opens up a world of possibilities. Founded in 2017, the Los Angeles–based SaaS company is on a mission to democratize access to world-class mobile commerce tools for every brand. A big part of making that happen is its partnership with Bitrise. Few people have seen the evolution of that partnership more closely than Sahand Ansari.

Every Android developer has been there: yesterday's build finished in 2 minutes, but today's identical build takes 8 minutes. You check your code - nothing major changed. You check your environment - everything looks the same. So why the massive difference? Without visibility into what actually changed between builds, debugging performance issues becomes guesswork. You're left wondering: Which tasks didn't come from cache? What inputs changed? Why did this specific compilation task take so long?

If you're part of a GitHub shop evaluating Bitrise for your mobile app teams, you might be hearing a familiar objection: "Why add another tool? GitHub Actions is our org standard, and it will work for mobile." It's a reasonable point. Nobody wants to maintain a snowflake system that sits outside the approved tool list. But here's the thing — it doesn't have to be GitHub Actions *or* Bitrise. The reality is that mobile CI/CD has unique demands.

Having a build cache solution is a powerful way to speed up builds, especially at scale. Bitrise Build Cache already accelerates builds across multiple ecosystems, but to get the most out of it we also need to optimize the build cache clients themselves and ensure stability across changing network environments. In this blog post, I’ll walk through the steps we took to improve stability and performance for Bitrise Build Cache customers.