Are private frameworks supported on iOS?

Question

Recently, I began to modulate my applications much more aggressively than before, dividing code fragments into frameworks or libraries.

I like the concept of "private frameworks" on the Cocoa desktop, i.e. framework included in the application package. From my little experience, frameworks are better suited for code reuse than simple libraries, since frameworks can include their own headers. This makes it easy to add a new structure to an existing project.

The problem is that these "private" frameworks are not supported on iOS. You must have static libraries there, and managing headers is a pain. Is there a good technical reason for Apple not supporting iOS frameworks?

(Just to make sure: Apple, unfortunately, uses the term “private infrastructure” for two things. Firstly, these are the “customizable” frameworks that come with the application, and secondly, these are undocumented and forbidden frameworks that people should not use on iOS. I ask about the first.)

PS. Is this a change in iOS 8? Theres Cocoa Touch Framework Template in Xcode 6.

Answer 1

It seems like custom frameworks are now supported by Xcode 6 :

IOS developers can now create dynamic frameworks. A framework is a collection of code and resources for encapsulating functionality, which is valuable for several projects. The framework works great with extensions, sharing logic, which can be used as the main application and related extensions.