Summit Session 1 - Adding support for Swift Package Manager
summary
Migration work migrates Flutter iOS plugins from CocoaPods to Swift Package Manager, with Flutter adding a package.swift manifest, a changed directory layout and optional Darwin folder consolidation for iOS/macOS. Tooling includes Flutter tool feature flags to run CI twice (CocoaPods on and off) and an analysis of all pub packages to find CocoaPods users; CocoaPods is moving to read‑only so automation is hard, migration is manual but feasible and apps can temporarily support both systems.
AI-written summary · about
chapters (21)
- 0:00Swift Package Manager intro
- 1:06Flutter iOS plugin migration
- 2:10CocoaPods vs SPM differences
- 3:14CocoaPods read-only deadline
- 4:39Automated migration tool
- 6:03Plugin author maintenance
- 7:49SPM benefits over CocoaPods
- 8:52Dual support testing
- 10:39SPM testing feature flag
- 12:49Add-to-app SPM limits
- 13:54Monetization for Flutter packages
- 15:41Legacy deps forcing SPM
- 18:38Community CocoaPods pain points
- 21:47CocoaPods deprecation plans
- 25:26Plugin migration steps
- 27:12SPM consumer experience
- 28:54Darwin folder support
- 29:57Mixing CocoaPods and SPM
- 31:00Xcode SPM versioning
- 33:05Objective-C to Swift migration
- 34:08Action items and follow-up
related talks
30mFrom CocoaPods to Swift Package Manager
45mSwift, Frameworks & Modules, Learnings from CocoaPods
37mCut costs, not corners: Master modularization with SPM
44mSwift Packages - Dependency Management of the Future
01h 13mDo iOS Panel, hosted by Antoine van der Lee
25mBuilding with SwiftPM
29mWarm Up
15mFirebase for Apple developers: What you should know