Apple is preparing a major move for those who prefer to use a wearable that is not from the house. In the first developer beta of iOS 26.1 Clues have emerged that third-party watches could integrate with the iPhone much more fully, to the point of behaving largely like a Apple Watch.
This shift is not a whim. The European Commission, within the framework of the DMA, demanded that Apple enable real interoperability with accessories outside its ecosystem. Although with reservations, the company accepted and set an approaching deadline. The iOS 26.1 code already reveals references to a notification forwarding and other hooks that would pave the way.
What would change and when could it arrive?
Anyone who has used an Apple Watch knows that its integration with the iPhone is complete: notifications, data from the Health app, Handoff between devices and even, in watchOS 26, workout metrics visible on iPhoneUntil now, many of these advantages were not available to other iOS-connected watches.
According to sources such as Macworld, beta 1 of iOS 26.1 It includes internal threads that mention the option to forward iPhone notifications to non-Apple accessories. The text suggests that the user could choose which apps have permission to send notifications to the wearable.
The key to all this is that it stops being a mere mirror of notices and becomes a system-controlled channel, with granular permissions and behaving similarly to how it does today WATCH with your paired iPhone.
While the finding is promising, it is not definitive: Apple could introduce the feature in iOS 26.1 or postpone it. The agreement with Brussels sets the deadline for the end of 2025, so if it doesn't arrive in this version, it could do so in a later one. iOS 26.2 later without deviating from the planned schedule.
How it would work: forwarding and re-pairing
The setting of «Forwarding notifications» would allow you to activate or deactivate, at will, the sending of notifications from the iPhone to an external device. The code suggests that only an active accessory at the same time, avoiding duplications.
Another relevant detail: by activating this forwarding, the Apple Watch notifications would be disabled. This way, notifications would be displayed on a single wearable, reducing noise and avoiding receiving duplicate alerts.
Among the internal references appears the term AccessoryExtension, which points to a pairing method and expanding capabilities between iPhone and third-party accessories. This would be a more in-depth approach than traditional Bluetooth connectivity, similar to the quick-pairing systems that already exist on other platforms.
This model would open the door for manufacturers offer an experience more similar to the native one, with permissions managed by iOS and an integration less dependent from each brand's own app.
Europe as a trigger, potential global impact
The demand of the European Commission is the great catalyst: effective interoperability with iOS is required so that consulted devices can interact with notifications and other system functions. Along the same lines, Brussels has also highlighted areas such as AirDrop-type file sharing within the expanded ecosystem.
Although the origin is European, a wider extension is not ruled out. In the United States, the Department of Justice has already pointed out certain limitations with third-party smartwatches, so Apple could opt for a broader rollout to simplify support.
It is advisable not to mix debates: this does not imply that the Apple Watch is compatible with AndroidThere are no signs that Apple will open that door, and there is no formal regulatory request to that effect.
If interoperability improves in iOS, it will be up to the manufacturers to decide how far they take their features and what advanced experiences put on the table in their apps and services.
What remains to be confirmed and what can we expect?
For now, the feature is not available to the public and the code remains ambiguousApple could enable these capabilities gradually, starting with notifications and adding additional permissions or APIs later.
The schedule is also unknown. The beta of iOS 26.1 It is already showing signs, but the company has a margin until the end of 2025. If it does not arrive in this version, it could do so in the next iteration, without losing the commitment to the DMA.
The actual experience will depend largely on the support that the developers themselves add. watch makers. With system APIs and improved pairing, fragmentation would be reduced and the user experience would be closer to that of an Apple Watch, with the logical differences of each platform.
For the user, the immediate benefit would be to regain basic functions such as viewing iPhone notifications with reliability and granular control, and lay the groundwork for future richer integrations provided that Apple and partners enable the necessary permissions.
If the pieces fit together, iOS 26.1 could be the first step toward a tangible opening: third-party watches more useful with the iPhone, regulation-driven interoperability, and a horizon where the user can choose their wearable without sacrificing key features.
