Hacker News Reader

API becomes a contract, documentation or not. There is blowback when the contract changes. This blowback is what stops unstable API from becoming public. Brreaking change for ApI used by 10k devs? Big blowback.

Wouldn’t this lead to a pretty fragile user experience across versions? I don’t think the parent is saying it’s technically impossible, but Apple isn’t about to open up an API they intend to immediately break, affecting not only devs, but their end users, tarnishing their image of stability (yes, even if it’s a 3rd party). Documenting these shifting APIs would also be a royal PITA.

Yes there is: if it’s there, people will use it and their apps will break if Apple changes the API.

It's technically possible, yes. But there are a lot of other considerations which may not "stop them" from doing it, but can still make it look like a bad idea.