Systems | Development | Analytics | API | Testing

Your CI pipeline worked fine when the app was young. Then the app grew. Features got split into modules. Teams formed around those modules. And somewhere along the way, what used to be a 4-minute build became a 25-minute one. Then 35. Now nobody pushes to main before lunch because the queue is already backed up. If this sounds familiar, you are not alone. According to Google’s 2024 Developer Survey, 83% of Android apps over 500,000 lines of code struggle with build performance.

Over-the-air (OTA) updates are one of the most powerful tools available to React Native teams. The ability to push changes directly to users’ devices without App Store review, without Google Play approval, without any action required from the user, meaningfully changes how fast a team can respond to bugs and iterate on their product. But OTA updates operate within clear boundaries. Misunderstanding those boundaries leads to two distinct problems.

CodePush is a great way to ship over-the-air (OTA) updates, avoid app store approval delays, and roll out changes cautiously. Even though App Center has closed down, there are many options available to get started with CodePush. But some of the default settings can create unwanted behaviors, stopping updates from installing or making the app look like it’s crashed.

CodePush is a great way to ship over-the-air (OTA) updates, avoid app store approval delays, and roll out changes cautiously. Even though App Center has closed down, there are many options available to get started with CodePush. But some of the default settings can create undesirable behaviors, leaving teams wrongly thinking CodePush causes a bad user experience.

There is a specific kind of dread that comes with finding a critical bug in a production React Native app. The fix is usually straightforward: a broken API call, a logic error, a UI state that did not account for an edge case. You can see exactly what went wrong and exactly how to correct it. The code change might take an hour. What takes days is everything that comes after. App Store review. Google Play review. Waiting. Watching your crash reports climb.

GitHub Actions is one of the best CI/CD platforms available today. For web apps, backend services, and infrastructure automation, it’s hard to beat. Deep GitHub integration, a massive marketplace of community actions, flexible YAML-based workflows, and a pricing model that’s generous for open-source projects. There’s a reason it dominates. But if you’re building mobile apps, especially for iOS, GitHub Actions starts to fight back. Not because it’s a bad tool.

If you’ve shipped a React Native app to production, you already know the feeling. A bug surfaces. Users are reporting it. Your fix is written, tested, and ready to go. And then you wait. Two days. Sometimes three. Occasionally five. App Store review doesn’t care that your ratings are dropping or that your support queue is filling up. It moves at its own pace, and your users experience every hour of the delay. CodePush over-the-air (OTA) updates change that equation entirely.

For teams using CI/CD, the specs of the build machine can have a significant impact on development productivity. Faster builds mean shorter fix-and-verify cycles, which speed up the overall development process. However, it’s hard to know how fast each CI/CD service actually is without comparing them under the same conditions. In this article, I compare the iOS build speeds of GitHub Actions, Bitrise, and Codemagic using the same Flutter project, and compare them in terms of cost-performance as well.

If you’re a mobile developer running builds on Jenkins, you already know the drill: a flaky agent goes down on a Friday afternoon, your Xcode version is three months behind, and the DevOps engineer who set the whole thing up left six months ago. The builds ship eventually - but at what cost? Jenkins is a powerful, battle-tested automation server. For teams building web backends or managing complex polyglot pipelines, it earns its place.

Jenkins has earned its place at the center of enterprise CI/CD. For organizations building backend services, orchestrating multi-stage deployments, and managing complex polyglot pipelines, Jenkins delivers the flexibility and control that engineering teams depend on. Ripping it out isn’t a conversation most organizations want to have - nor should it be. But mobile is different.