Reusable iOS Frameworks |

If you have found yourself writing the same code over and over again for multiple different apps, then this is the course for you. Learn about the different ways to store your reusable code for a Swift project, how to write methods and functions in a reusable way, and how to think about your end user as a developer rather than a user by focusing on API design principles and access control.

This is a companion discussion topic for the original entry at

Hi @dokun1, first that anything congratulations for such amazing course.
Really enjoyed it!!

How do you handle the scenario where the main functionality of you framework requires 3rd party framework in order to work properly?


Hi @jecht83 - thank you so much for your kind words! I really appreciate it, and I am glad you enjoyed the course.

Generally speaking, you want to try to avoid having dependencies that have dependencies themselves - however, this eventually becomes something you’ll have to deal with. A Swift Package has the ability to handle sub-dependencies in the Package.swift file, if something can be imported as a Swift package itself. For a Cocoapod or something you ship with Carthage, you would want to make sure you have a sample application that handles your framework gracefully with the sub-dependencies integrated manually.