Swift Package Manager vs. CocoaPods: Which is Right for Your iOS Project?

• DG
  dev_guru October 26, 2023, 10:15 AM

  Hey everyone,

  I'm starting a new iOS project and I'm trying to decide between using Swift Package Manager (SPM) or CocoaPods for dependency management. Both have their pros and cons, and I'm keen to hear from others who have experience with both.

  I know SPM is now integrated directly into Xcode and is the native solution from Apple. It seems simpler for smaller projects and directly leverages Swift's ecosystem. On the other hand, CocoaPods has been around longer and has a vast repository of libraries. I'm also a bit concerned about the build times and complexity that can sometimes arise with CocoaPods.

  What are your thoughts? When would you choose SPM over CocoaPods, and vice-versa?

  Looking forward to your insights!

  👍 Like 💬 Reply
• RK
  rachel_k October 26, 2023, 10:35 AM

  Great topic, dev_guru!

  I've been leaning towards SPM for most of my recent projects. The native integration is fantastic, and it feels more streamlined. For example, managing local dependencies or private packages is much easier with SPM. I also appreciate that it's built with Swift in mind, which can lead to better type safety and integration with Swift features.

  However, I still find myself reaching for CocoaPods when I need a dependency that hasn't yet adopted SPM. The sheer number of libraries available via CocoaPods is still unmatched, although this gap is closing rapidly.

  One thing to consider with SPM is that sometimes it can be a bit fiddly with older Xcode versions or certain build configurations. But generally, for new projects starting today, I'd recommend SPM unless you have a specific library dependency that mandates CocoaPods.

  👍 Like 💬 Reply
• JC
  john_c October 26, 2023, 11:02 AM

  I'll echo what rachel_k said. SPM is definitely the future, and for any new development, it's the sensible choice. The performance improvements in recent Xcode versions for SPM are also noticeable.

  My main reason for still using CocoaPods is legacy projects. Migrating a large, established project from CocoaPods to SPM can be a significant undertaking. There's also the ecosystem of tools built around CocoaPods (like some CI/CD integrations) that might require updating.

  For those new to dependency management, SPM's simplicity is a huge advantage. You just add the package URL and version, and Xcode handles the rest. No need to maintain a separate Podfile and run pod install.

  If you're working with a team, ensure everyone is on the same page regarding the chosen dependency manager. Consistency is key!

  👍 Like 💬 Reply
• MS
  mike_s October 26, 2023, 11:25 AM

  What about build times specifically? I've heard that SPM can sometimes be slower for large projects with many dependencies compared to CocoaPods, especially when not caching effectively. Any empirical data on this?

  Also, how does each handle pre-compiled binary frameworks? SPM has native support, but CocoaPods has mechanisms too.

  👍 Like 💬 Reply
• DG
  dev_guru October 26, 2023, 1:10 PM

  Thanks for the replies everyone! It seems the consensus is leaning towards SPM for new projects, with CocoaPods still relevant for legacy support or specific library availability. I'll definitely keep the build times and binary framework handling in mind.

  For mike_s, I've seen mixed results on build times. My personal experience is that SPM's indexing can be a bit slow initially, but subsequent builds are often faster than CocoaPods, especially with recent Xcode versions. However, this can depend heavily on the project structure and the number/complexity of dependencies.

  I'm going to try out SPM for my new project and see how it goes. If I hit a roadblock with a critical library, I'll re-evaluate.

  Anyone else have strong opinions or specific use cases where one clearly outshines the other?

  👍 Like 💬 Reply