Top Rated CocoaPods Alternatives
Cocoapods is simple to use and setup even for beginners. You can just import the library after the installation without any special tweak or configuration on you project. Review collected by and hosted on G2.com.
Sometimes it takes a lot ot times when build tasks of project, it also install almost whole folder project include example at repository Review collected by and hosted on G2.com.
20 out of 21 Total Reviews for CocoaPods
It is easy to use and most of the extra package available. It is straightforward to impement and use packages. It is like it is part of your own code base and you don't have to worry about keeping up to date. Review collected by and hosted on G2.com.
Now it is not as relevant after swift packages but it is stil the easiert and the most common way to impement and distribute packages. Review collected by and hosted on G2.com.
Very simple to add/update without having to do anything manually.
Its the most easy way to include a lot of functionality to your project.
here is a pod for that. Review collected by and hosted on G2.com.
Had to improve the swift approach now that Swift Packages exist Review collected by and hosted on G2.com.
Setup is easy (and I was a beginner with iOS) and version control as well.
Its Swift compatibility is on point, and is pretty much used by that community.
A lot of open-sourced libraries.
Overall - quite a nice tool for handling your dependencies when you are a beginner with iOS development. Review collected by and hosted on G2.com.
Slow-ish on installation and updates, could probably improve that.
Maybe a bit messy when creating your own pods/dependencies for publishing.
You don't get a notice when someone removes a dependency you used to use and cannot install it.
Not sure if I can tell whether the pod is functional before actually installing it.
At times there are backwards compatibility issues. Review collected by and hosted on G2.com.
It saves time and effort in implementing dependencies. It has an ease of use. Saves time, many things are automatically done. There is no need that you do it manually. Ease of deletion, Light repo Folder. Review collected by and hosted on G2.com.
Sometimes, different versions of Xcode create difficulty in implementation and the instalment or update of the pods becomes difficult. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
Cocoapods has a very large and active open source community that constantly is improving and updating. The only downside is that sometimes with so many cooks they can make changes for a new macOS version or subversion. This means they sometimes can break compatibility with an older version and not notice due to not having a paid QA constantly checking. While they do fix bugs fast, occasionally you'll be at the mercy of their git issue tracker to find out whats going on. Review collected by and hosted on G2.com.
Actually, the only thing for me is that we have a lot of libraries open-source that added to Cocoapods. Review collected by and hosted on G2.com.
- My git changes will be +1000 files
- I am forced to work with workspace not just staying with xcodeproj
- I can't know if a pod is working or not till I download it and build the project, why not having like CI to build the pod on the server and tell us if there is a problem with the pod or not.
- It's unsafe, sometimes the user removes the pod and I keep gussing what is the problem, why I can't install this pod anymore. Review collected by and hosted on G2.com.
Implementation of the CocoaPods is straight-forward, and my personal opinion: CocoaPods is way better then Carthage and other dependency managers. Review collected by and hosted on G2.com.
In the past, I have dozens of problems with compatibility of the iOS version with particular libraries. So, I need additional time to figure it out, which library should be updated or not, regarding on iOS version. Review collected by and hosted on G2.com.
Almost every iOS library out there supports CocoaPods. Great community & active development. Review collected by and hosted on G2.com.
So much configuration (albeit managed) when compared with SPM. Review collected by and hosted on G2.com.
The best things it’s provide detailed level installation process for how to use library in project.Easier to use. Review collected by and hosted on G2.com.
there it’s take some to update libraries accordingly to new Swift version issues a lot of issue face for compatibility. Review collected by and hosted on G2.com.
