Cocoapods is an Objective-C library dependency manager that allows developers to specify dependencies and their versions in a Podfile. It supports private pods through custom spec repositories that can host podspecs for any code, allowing pods to be installed from git repositories, URLs, or local paths. Using many small, decoupled dependencies promotes modular code while avoiding overly broad dependencies. Developers should carefully consider potential dependencies based on metrics like commits, issues, and code quality.

1. Practical Cocoapods
@MicheleTitolo

3. Objective-C Library
Dependency Manager

4. Specify Dependencies

5. Specify Versions

6. Dependency Resolution

8. Private Pods

9. Yes, this is a thing

10. Theory

11. You can add a .podspec
to anything

12. Any remote can be a pod

13. 2 options

14. Your own Spec repo

15. └── [SPEC_NAME]
└── [VERSION]
└── [SPEC_NAME].podspec

16. $ pod repo add NAME SOURCE_URL
$ cd ~/.cocoapods/NAME
$ pod repo lint .

17. Don’t need a private fork of
CocoaPods/Specs

18. Any code, anywhere

19. Specify any remote
that has a .podspec

20. pod ‘BananaLib’, :git=>git@github.com/…

21. Podspecs should be in the root
folder of the repository

22. Specify a .podspec

23. pod ‘BananaLib’, :podspec => ‘https://…’

24. Specify a path

25. pod ‘BananaLib’, :path => ‘~/Projects/…’

26. Modular Code

27. Smaller dependencies

28. Independent pieces

29. Decouple

31. More dependencies

32. “Dependencies are bad!”

34. Choosing dependencies

36. Commits

37. Stars, Watchers, and Forks

38. Open : Closed Issues

39. Pull Requests

40. Look at the code

41. In Summary

43. Thank You
@MicheleTitolo