Implementation of the CocoaPods is straight-forward, and my personal opinion: CocoaPods is way better then Carthage and other dependency managers.

Repos can have a lot of files and content that are not necessary to build and include a framework. Travis and CircleIO configurations, test files and data, and old left over code are but a few examples of unnecessary files and clutter that tend to come with a majority of package/dependency managers. The primary reason being that they download the entire repo. With Cocoapods the developers of frameworks specify the exact files needed to build each release. With a larger project this can make a major difference when searching during debugging. Additionally Cocoapods offers submodule like behavior. Where Carthage and Swift Package Manager only allows one framework per source. Cococapod allows many sub targets/frameworks. This is great for creating a core API SDK and adding sub-frameworks that, for instance, may add authentication specific code for a specific project.

The best things it’s provide detailed level installation process for how to use library in project.Easier to use.