What is the advantage of adding shared modules into IOS via Cocoapods ? Is there any performance/capability benefits ? I saw many repo that use Cocoapods for that but couldn’t find any explanation why
Sebastien Leclerc Lavallee
01/19/2021, 2:45 PM
I would say ease of integration. It's pretty much the same as adding any other dependency. The advantage is there if you already use Cocoapods, which is my case.
01/19/2021, 2:57 PM
If you’re developing a library/framework that you’re going to provide to usual iOS developers, you’re better of providing them the dependency through cocoapods as that’s something they’re used to already thus helps reduce adoption friction
01/19/2021, 3:03 PM
@kpgalligan has been looking closely at this area as well...at least in terms of options for sharing/accessing pre-built binaries vs having iOS devs needing tooling etc installed to allow building locally
hmm, actually meant to reply to different thread with similar but slightly different question 🙂 anyway, might apply here too
01/19/2021, 3:47 PM
That's an ongoing topic. We don't really have anything public right now (not a ton private either that isn't part of the clients' build code), but thinking through it. We use cocoapods for ease of integration, but our current builds still require building locally. Some teams are dead set against building kotlin locally for iOS devs, others don't mind so much. We're looking into building something where you essentially point a build tool at a git(hub) repo and it'll run CI to publish dependencies for iOS (Cocoapods, SPM?) and NPM (probably), but haven't touched that yet.