- Building a great smartwatch experience on iPhone is much harder than on Android, and the situation has worsened over 8 years.
- Third-party smartwatches cannot send text messages, reply to notifications, or perform actions like dismissing or muting on iOS.
- iOS lacks interprocess communication (IPC) like Android, forcing clunky SDK solutions that other apps dislike.
- Closing the iOS app disconnects the watch from the internet and the app, limiting functionality.
- The watch cannot detect if the phone is being used, so notifications always buzz even when staring at the iPhone.
- Apps must go through Apple App Store with risk of arbitrary rejection, and sideloading is not possible.
- Enabling third-party developers to charge for watchfaces or apps is difficult due to App Store rules.
- JavaScript engine restrictions forced complex workarounds (compiling a JS cross-compiler inside the iOS app).
- Developer mode terminates every few minutes, making testing and development frustrating.
- Past efforts like an SMS-over-IP deal with AT&T resulted in poor user experience (messages not appearing in iMessage).
- iOS 13 added restrictions requiring full notification previews on lockscreen for third-party watches.
- Apple blocked carrier messaging deals unless iMessage is turned off, limiting third-party options.
- Apple's restrictions are anticompetitive, reducing competition, increasing prices, and stifling innovation (supported by DOJ and class-action lawsuits).
- Despite 40% of users being iPhone owners, the iOS app will have limited functionality compared to Android.
- Users are encouraged to complain, switch to Android, or support legislation like ACCESS Act, AICO, and DMA.