We all have done it. When working on something you find a piece of code that could be extracted into a separate library. Lets call it furry-guide. Furry-guide could also be useful for other developers and as a good open source contributor you upload it to GitHub. You also make sure that it can be used with popular dependency managers.
As you were developing furry-guide in parallel with the main app, you included some of your favorites libraries as dependency to it. Maybe you just wanted to used that awesome logging framework you use everywhere. Or you needed some networking functionality and marked Alamofire version 4.1.0 as dependency for furry-guide.
Overall this should not be an issue. These dependencies are you go to helpers. In every project where you will be using furry-guide, they will be included anyway. So there is no real overhead. It’s just convenient.
By defining these dependencies to furry-guide, you have created a small hurdle for using it. Maybe I’m using different logging library and now furry-guide will pull in extra one not used anywhere else. Maybe I need a different version of Alamofire? Or I’m using URLSession everywhere.
When working on Find movies to watch, I decided to create some components as separate libraries. iTunesSearch for finding movies on iTunes. TheMovieDatabase for getting movies lists. ImageProvide for posters fetching and caching. All these needed two common functionality: logging and network.
For images fetching and caching I have an earlier attempt CDYImagesRetrieve, that declared AFNetworking as dependency. And it had preprocessing macro for enabling logging. Now I wanted to do it better.
Solution that I came up with was to define protocols for these, that app can inject. For example app defines logging protocol:
On app side you need to create a logger:
And inject. Only if you need it.
This gives the control over logging to application developer. Developer decides if library logging should be enabled and where the output goes.
Same pattern is used for networking. Library defines a protocol:
On app side you define library requests handler:
And inject it into API client:
This gives application developer control over how these requests should be made. Additionally it allows developer to prioritize app network calls over library network calls.
Give power to developers 🤘
Tags: ios, swift, dependency, design, library, programming