Systems | Development | Analytics | API | Testing

A React Native build is really two builds stacked on top of each other. On Android, Gradle compiles your Kotlin and Java, then drops down into cmake and ndk-build to compile the C++ that ships inside Hermes, Folly, ReactCommon, and your own turbo modules. On iOS, Xcode does the equivalent: Swift and Objective-C on top, the same C++ underneath via Clang. Two build systems, two languages on top, one shared set of C++ underneath.

‍Build Cache can meaningfully shorten CI feedback loops, but only if it’s connected to workflows where it’ll actually make a difference. So how do you figure out which workflows will benefit? That’s the part that’s been easy to get wrong — until now. Quick Connect is a new feature that takes the guesswork out of estimating time savings: it looks at your last 30 days of build data and surfaces the workflows that will benefit themost from caching.

WWDC 2026 delivered plenty for app developers to talk about, but some of the most consequential announcements were aimed squarely at the people running the infrastructure underneath. We've already covered the under-the-radar announcements for iOS developers and what Xcode 27's Device Hub means for CI/CD. This one is for the fleet operators. If you run Mac infrastructure at any scale, the Virtualization framework is already part of your life. On Apple Silicon, it's the only way to run a macOS guest.

If you're building iOS apps on Bitrise and using one of the Xcode 26 edge stacks, you must switch to the Xcode 26 stable stack before July 31, 2026.