We should remember that "development frameworks" were not even allowed in the early days of iOS [1]. That we can use them now is a huge step forward. But at the same time, little prevents companies like Apple from throwing the switch back for new apps.

[1] https://www.apple.com/hotnews/thoughts-on-flash/

Quoting from [1]:

> We know from painful experience that letting a third party layer of software come between the platform and the developer ultimately results in sub-standard apps and hinders the enhancement and progress of the platform. If developers grow dependent on third party development libraries and tools, they can only take advantage of platform enhancements if and when the third party chooses to adopt the new features. We cannot be at the mercy of a third party deciding if and when they will make our enhancements available to our developers.

What many forget when quoting iOS victory about Flash, is that Adobe was quick to adapt and offer AOT compilation for Flash.

So many of the casual games in iOS kept being Flash, before Unity and Cocos got enough uptake.

This seems to be a quote taken out of context. Apple wasn't against third party frameworks as a rule — plenty of third party libraries and tools popped up, especially for allowing languages other than ObjC to be used effectively on iOS.

The message in Thoughts On Flash wasn't about third party libraries wholesale; it was refuting the expectation that Apple should special-case Flash, a technology that never ran acceptably on Android and was quickly deprecated, never mind on iOS.