Building and Integrating Frameworks
summary
Integrating third‑party iOS frameworks is a hands‑on checklist: require a sample project that builds, headers and simulator slices included, explicit third‑party dependencies listed, configurable logging and no stealthy swizzling, and test for idle memory and network usage; frequent failures cause 64 emails over a month during one integration; prefer use a universal static framework for wide production SDKs, limit dynamic frameworks to ~6 to avoid startup cost, and note Swift Package Manager builds static by default.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:32Super Engagement Tracker
- 7:55The Seaworthy Framework Checklist for Vendors
- 14:32WWDC 2016 Optimizing App Startup Time
- 22:15Story Time
- 37:06Frameworks State of Affairs
- 38:34Frameworks State of Af s
related talks
45mSwift, Frameworks & Modules, Learnings from CocoaPods
30mA Micro-services perspective on iOS architecture
32mCut costs, not corners - Master modularization with SPM
44mMake your project great again
28mLessons From Becoming an SDK Developer
04mThere is an extension for that
44mSwift Packages - Dependency Management of the Future
45mTooling in Swift - Xcode Integration & CI