When Apple uses private APIs that are forbidden to developers on the App Store to compete with them it's not exactly fair.
So I wouldn't say it's a failure that they don't do that even more often.
So I wouldn't say it's a failure that they don't do that even more often.
That said, I'd love to see them take an approach unstable API release that requires the app to show a warning like "This app relies on unfinished features that may change or stop working entirely in the future, requiring the seller to release an apo update." and require them to launch it as a free preview, make it refundable during this period, etc.
2) This is a solved problem. You throw a “this is an experimental API, it’s interface may change”
iOS 7 was released in 2013. 13 years ago, aeons in tech land.
So "APIs are hard to get right the first time. I could see why they wouldn't want to release one until they've dogfooded and refined it." is crap. They're hoarding private API access purely for competitive advantage in services.