3rd party tools and frameworks you use in your applications and why
summary
Teams report using XcodeGen, SwiftGen, SwiftLint to avoid merge conflicts and keep resources/formatting consistent, and common runtime libs like Alamofire, PromiseKit, Realm for networking, async and storage; prefer few heavy deps, commit or fork sources for longevity, and push analytics through a backend or Segment to avoid SDK bloat. Package manager choice matters: SPM lacks build-scripting today so people still use CocoaPods/Carthage or drag xcframeworks, and many switch to xcframeworks to avoid slow debug builds and M1/tooling breakage.
AI-written summary · about
chapters (16)
- 0:00Managing project dependencies
- 2:50Risks of third-party tools
- 4:45Balancing native vs. external
- 6:41Designing for maintainability
- 9:27Corporate dependency policies
- 13:00Contribution and ownership
- 16:01The cost of abstraction
- 19:08Real-world migration stories
- 21:45Tooling and build automation
- 25:23Package manager comparison
- 30:57The future of SPM
- 33:46Security and auditing
- 40:11Privacy and analytics
- 43:47Strategies for analytics
- 48:41Selecting quality tools
- 52:30Naming and closing remarks
