IOS application development architecture

I have been developing IOS for nearly two years and have written a lot.Code, Has done a lot of projects. I will share with you the architecture of the IOS application.

This article is my opinion. If you have any concerns, please leave a message.

My IOS Application Development Structure

The overall structure is clear and is a tree structure.

1About coreengine

The data returned by the server reaches the net layer. The net layer is transmitted back to coreengine through the delegate protocol, that is, coreengine implements the delegate protocol for the net layer.

2And any event has two sides,Design patterns cannot be abused. Take the singleton as an example. It is convenient and has only one object. Therefore, many sample codes use it to pass values. Since the header file can be directly used, this damages the overall framework of the software and improves the coupling between modules. Therefore, it is a good choice to develop a third-party library and provide functions to developers in the form of a singleton. However, if you are developing a product directly, we recommend that you do not design a singleton, unless your project is very small or used as a Tool class.

Statement: The above is my opinion

Original blog: http://blog.csdn.net/yjh4866