Apple seeded iOS 26.5 and iPadOS 26.5 beta 4 on April 27, build 23F5069b. There are no significant new consumer features in this release — no Siri updates, nothing visible for end users. What the beta does advance is two areas directly relevant to developers building for the European Union: the Digital Markets Act interoperability APIs for third-party wearables, and the infrastructure for Apple Maps advertising.
What the EU Wearable APIs Enable
The third-party wearable features are available for testing in the current beta, but only for developers and users in the European Union. For the first time, manufacturers of non-Apple earbuds, smartwatches, and headphones can access three capabilities previously reserved for the Apple ecosystem:
Proximity pairing: Automatic pairing when a compatible accessory comes near an iPhone, matching the AirPods experience. Users see a pairing prompt without going through Bluetooth settings manually. For hardware makers, it closes the first-use gap that has historically favored Apple accessories.
Notification forwarding: Notifications arriving on iPhone are forwarded to a paired third-party smartwatch. Users can view and interact with them from the accessory, the same way Apple Watch handles them. The exact scope of interactions depends on the hardware maker’s implementation.
Live Activities: Real-time iPhone activities (navigation steps, delivery tracking, live sports scores, timers) are forwarded to the paired wearable. For app developers, this is the most immediately actionable feature: if your app already uses ActivityKit, the forwarding to EU third-party wearables works without code changes.
These are not voluntary additions from Apple. The Digital Markets Act requires iOS to open interoperability interfaces to third-party manufacturers on request. Apple introduced the first set of these APIs in iOS 26.3 and has been extending them through the iOS 26.5 beta cycle.
How to Prepare in the Beta, Depending on What You Build
If you build apps with Live Activities: forwarding to EU third-party wearables requires no code changes. The practical thing to verify is how your activity layouts render on display sizes and resolutions that differ from Apple Watch. Testing against third-party devices in the current beta is the best way to catch layout issues before the iOS 26.5 public release.
If you manufacture hardware: access to the DMA interoperability APIs goes through a formal request to Apple — it is not open enrollment. The process is outlined on the Apple interoperability request page, where you describe your device type and use case. Requests can be submitted now, ahead of the public release.
If you build companion apps for accessories: the new DMA pairing flows may intersect with Bluetooth-based or app-assisted pairing flows you already manage. Worth reviewing whether the proximity pairing path creates any conflicts with existing connection logic.
Geographic Scope and Limits
Proximity pairing, notification forwarding, and Live Activities for third-party wearables are EU-only. Outside the EU, the Apple accessory ecosystem remains closed to non-Apple devices. Apple has given no indication it will extend these features to other regions without regulatory requirements equivalent to the DMA.
Detailed technical documentation on the underlying frameworks is not yet public. Apple has communicated what the features do, not the low-level API surface.
The Rest of Beta 4
The beta also includes code that lays groundwork for Apple Maps advertising — strings referencing “Maps may show local ads based on your approximate location” — with no visible UI for end users yet. The public Maps ad launch is confirmed for summer in the U.S. and Canada.
RCS end-to-end encryption between iPhone and Android is back in testing: it appeared in early iOS 26.4 betas, was removed before the public release, and has returned in iOS 26.5. Apple has not committed to a release date.
The iOS 26.5 public release is expected in late May or early June 2026, likely timed alongside the Maps ad launch. At the current pace of one beta per week, beta 5 should arrive around May 4–5.
