Systems | Development | Analytics | API | Testing

Why the real device versus virtual device debate is the wrong frame for engineering leaders and what the right one looks like.

The mobile sector has undergone massive transformations since the early days. What used to be a predictable verification exercise is now an intricate web of competing hardware manufacturers, custom firmware distributions, distinct chipset designs, and fast software update schedules. Modern software teams face hundreds of real-world variables every time they prepare a public build. Managing device fragmentation stands as one of the most demanding technical roadblocks in software verification.

That's Nathan Hillyer, Director of Engineering at ForeFlight, on what happened after his team started running their GitHub Actions workflows on Bitrise Build Hub. Until last month, trying that for yourself meant talking to sales first. That’s fine for a 300-person engineering org evaluating a CI overhaul, but it made no sense for the two-pizza team that just wants to know whether changing one line of YAML will meaningfully speed up their Xcode builds. That's fixed.

At Bitrise, we continually invest in security best practices to ensure that our customers' data stays safe and secure. As part of this ongoing effort, we are pleased to announce that we have successfully completed our 2026 SOC 2 Type II assessment, with no exceptions recorded in the final report. The report covers the period from July 1, 2025 to June 30, 2026 and is valid until June 30, 2027.

Namespace, Avrea, and Blacksmith are among the fastest GitHub Actions runner providers on the market right now. According to Avrea's August 2026 benchmarks, they all score within about 1% of each other on raw CPU. The same benchmark shows warm builds (populated cache) beating GitHub's default cold start (cache disabled) by anywhere from 5x to more than 140x, depending on the project.

Memory leaks are the bugs that really creep up on you. One minute your app is running perfectly, then suddenly it slows to a crawl or crashes. We don’t get a warning with memory leaks, so we need to prepare proactively and be ready when they hit. This means we need to: This guide is here for all of that.

Apple's iOS 27 release marks another significant shift in the mobile landscape. Beyond new features for iPhone users, it signals a familiar pressure point for QA and development teams: the clock starts ticking the moment the update goes live, and your apps need to be ready. Here's why that matters: nearly 80% of iPhone users adopt the newest iOS version almost immediately. That high adoption rate leaves little room for error. If your app breaks on the iOS 27 release, your customers notice fast.