iOS 27 ships with Xcode 27 and no dropped iPhones

Apple released six platform updates at once on September 14, 2026: iOS 27, iPadOS 27, macOS 27, watchOS 27, visionOS 27 and tvOS 27. Apple's announcement leads on speed and on a redesigned Screen Time. For developers, the more useful headline is what did not happen: no iPhone lost support.

MacRumors reports iOS 27 runs on iPhone 11 and newer, the same set iOS 26 supported. A major release that drops nothing is unusual, and it means your minimum deployment target does not have to move this year.

What actually shipped

Two updates matter to anyone who builds software and are easy to miss in consumer coverage. Scripting OS X lists Safari 27 and Xcode 27 alongside the operating systems, and records that macOS 27 is named Golden Gate with build 26A428.

Point releases went out on the same day for machines that cannot move yet.

Release	Version or build
macOS 27 Golden Gate	build 26A428
macOS Tahoe	26.7, build 25G229
macOS Sequoia	15.8, build 24H23
iOS and iPadOS, previous line	26.7
Developer tools	Xcode 27, Safari 27

That last row is the one to schedule around. A new Xcode arriving with the platforms is the usual signal that your build machines and your continuous integration images need a plan.

The speed claims, and who gets them

Apple's own figures are the three in the chart above. It also cites iPad file browsing and transfers up to 5 times faster, and Apple Vision Pro Wi-Fi startup up to 3 times faster.

Treat these as vendor numbers. They are worth testing rather than repeating, because a launch-time improvement usually depends on hardware, and the phones that benefit most are rarely the oldest ones you support.

Hardware requirements split the release in two. iOS 27 itself runs back to iPhone 11. Apple Intelligence features need an iPhone 15 Pro or newer, per MacRumors. Mac support starts at M1, and the iPad mini needs an A17 Pro or newer.

Where it is not available

Siri AI ships in English first. Apple says French, Japanese, Korean, Portuguese and Spanish arrive in October.

Two regions are further behind. Apple says Siri AI features are not available in the European Union at launch, and that some features are unavailable in China pending regulatory approval. If your user base is largely in either place, a feature built on these APIs is not something you can ship to everyone at once.

What this means for developers

Start with the compatibility win, because it is real and it is rare. Nothing was dropped, so the pressure to raise your minimum version this autumn comes from the APIs you want rather than from devices falling off. That is a better position to plan from than the usual one.

Then deal with Xcode 27. Update one build agent rather than the fleet, and rebuild an existing project on it before you change any project settings. Toolchain bumps surface warnings and deprecations that were invisible the day before, and you want to see that list on a machine you can roll back.

The Apple Intelligence split is the design problem worth naming. Consider what that feature needs: an iPhone 15 Pro, English until October, and no EU availability. That is not something to put on the critical path of an app used worldwide. Build it as an enhancement with a working fallback, and check what your app does on an iPhone 11 in Paris before you ship.

Finally, keep the point releases in your support matrix. Apple shipped macOS Tahoe 26.7 and Sequoia 15.8 on the same day. That says it expects a long tail of machines that will not move to Golden Gate soon. Enterprise fleets in particular sit on those versions for months. If you dropped older macOS support at the last major release, this is the pattern to weigh. It argues for watching how quickly a platform actually retires hardware before you follow suit.