If I want to modularize an iOS codebase, would you recommend creating one package with multiple libraries or multiple packages? Why? #Swift - ThreadSky

About ThreadSky

lucas.love • 16 days ago

If I want to modularize an iOS codebase, would you recommend creating one package with multiple libraries or multiple packages?

Why?

#Swift

Comments

rubiofung.bsky.social•16 days ago

Probably it depends on your project size and number or teams and people. For us at XING, we try to use one package per team containing all the related features they own. This also allows the teams to maintain hidden the complexity of their targets setup to other Package consumers.

kristofferjohansson.com•16 days ago

Having used both approaches, I prefer using a single package with multiple libraries.

In my experience, this setup works more reliably with Xcode. I also like having one package manifest to manage everything related to the project, like third-party dependencies etc.

kristofferjohansson.com•16 days ago

The `package` access modifier can also be quite useful in this configuration.

r.ozan.ski•16 days ago

I used to prefer multiple packages but now go for a single package: there’s only one Package.swift to maintain and all target sources are in sibling directories

r.ozan.ski•16 days ago

main downside is that if you have lots of targets your Package.swift can get pretty big, and navigating around target definitions isn’t the easiest. wish there was better integrations for this

r.ozan.ski•16 days ago

also I think if there were targets I could see being reused elsewhere maybe I would separate them into separate package(s) — I kind of treat this singular package as an app’s main, ‘private’ package

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply