|
|
|
|
|
by onesociety2022
3 days ago
|
|
I never understood how any regulatory body is going to decide which APIs in iOS must be made available to third-parties to hook into. So what if I'm a third-party maker of TCP/IP stack and I want Apple to offer me the ability to sell my custom TCP/IP stack to my iOS customers as a replacement for the stock TCP/IP stack that ships with iOS. Clearly no regulatory body has cared about that because it's too niche of a space? So some government official will scour the entire API surface of iOS and decide which ones Apple needs to expose to third-parties? They have already decided App Store and Payments APIs need to be made available. Now it looks like they also expect off-device foundation models need to be made available to third-parties. What about making Apple Watch specific APIs in iOS be made available to all third-party watch makers so any one can bring any smartwatch and use it just as effectively as the Apple Watch with an iPhone? What about all the AirPods specific APIs that lets Apple offer a better experience with AirPods than a generic bluetooth earbuds? What about Apple Pencil? And so on... If you go down this path, the list is endless. |
|
Don't threaten me with a good time? All of those seem like great policies. The fact that I cannot use an apple watch with an android phone is ridiculous, and vice versa as well.