Motivation

SDK can depend on external dependencies like alamofire.
Alamofire is really popular networking library and it may be used in the user application.
Having two different versions of the same library will cause conflict on build.
Users will need to change their version to comply with our version, which is not acceptable aproach.

This problem is really well described and mentioned in many bugs.
For example:
https://github.com/CocoaPods/CocoaPods/issues/461

We will need to figure out solution the same as we done on Android when we decided to use BOM version management.

How

We need to replicate the same work we have done for Android by allowing developers to avoid dependency problems or document how to handle that situations.