Systems | Development | Analytics | API | Testing

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.

We previously explored how Codemagic CLI tools can streamline iOS app deployment to App Store Connect with GitHub Actions. The Codemagic team has continuously improved these tools, extending their capabilities to Android releases on Google Play Console.

Have you ever found it a bit tedious to enter the same release notes text every time you submit an app for review in the stores? In this article, I’ll introduce a method to automate this small but repetitive task. It’s very easy to implement, so please read on.

In this article, I will introduce the steps to integrate Shorebird with Codemagic CI/CD, using the Codemagic Workflow Editor. You will be able to incorporate a workflow that allows code push of Dart code changes without requiring installation from the store. In the following example, changes to the text displayed in the user interface are reflected immediately.