What should I pay attention to in the SDK developed by iOS for third parties? Please advise.

If Apple comes with its own api and uses it as much as possible, the third party will definitely not be as good as Apple's own implementation.

Note that it is best not to let users see your source code.

Open interfaces should be flexible and clearly consider various usage scenarios. ?

When calling the third-party framework in SDK, we should consider the conflict problem.

Other considerations:

1. When naming class names, macro definitions, enumerations, notifications, categories, etc. Add a special prefix to the static library to avoid naming conflicts.

2. Chinese and French names in categories also need special prefixes to avoid unnecessary troubles caused by method coverage.

3. The methods in C and c++ in the project need to be prefixed.

4. For the open source libraries introduced when developing static libraries, if the quantity is too large, external references and explanations can be made when providing them to visitors. If the capacity is small, you can prefix the class names, enumerations and notifications used in the class.

5. It is particularly important to note that when there are multiple interfaces in the same class, all interfaces must be checked to avoid omission when adding prefixes.

6. Because some accessors strictly control the size of the app when introducing static libraries, they should simplify the code as much as possible when developing static libraries, and eliminate some unnecessary parts when introducing open source libraries, such as functions that can be realized by methods provided by the system, and try not to introduce large third-party libraries.