You owe me a new keyboard. Apple puts out half baked APIs constantly, and drops APIs constantly. Like literally, every release they do has APIs in those two camps.
Using this logic you should then ot have the freedom to read your emails outside Apple browser or email client on your computers, the solution is
1 let the user decide if the trusts the third party
2 for sensitive application like mail/sms/browsers review the top 5 alternative browsers/email clients etc and allow only those, I assume Apple has the ability to say discuss with Mozilla about allowing Firefox on iOS, what APIs and what privacy rules need to be respected and then have a team of lawyers ready if Mozilla breaches the contract/promises.
My point there are solutions between the extremes of not allow thrid party access and allow any random app access.
No one considers email to be secure because of if nothing else, the store and forward nature.
IMessage is end to end encrypted. Should Apple also allow third parties the ability to intercept iMessage or should they split iMessage from sms? Who does that benefit?
2. Now some developers are in a privileged position.
Apple has a long history of developing functionality and using it internally before releasing them publicly. The alternative is releasing a half baked API that it has to support forever. It’s a lot easier to change an API that is only used internally than it is to change an API which people depend on.
Yes, Apple produced a better solution than allowing random third parties the ability to record everything you do on your phone. Would you prefer that they never increase privacy and security?