Change is coming to Flutter. Starting with version 3.44, the framework officially swaps out CocoaPods for Swift Package Manager (SwiftPM) as the default dependency manager for iOS and macOS apps. What does this mean for developers? Less Ruby hassle, smoother builds, and a clearer path forward—but also some necessary migration steps. We’ve broken down the most important points into 10 key items to help you navigate the transition without breaking a sweat.
1. SwiftPM Becomes the Default in Flutter 3.44
With the next stable Flutter release—version 3.44—Swift Package Manager takes over from CocoaPods as the go-to dependency manager for Apple platforms. If you've been managing iOS and macOS dependencies through CocoaPods, you'll notice that the Flutter CLI now defaults to SwiftPM. This means no more fighting with Ruby installations or outdated CocoaPods versions just to run your app. The change is automatic for new projects, but existing ones will be migrated when you next build or run your app. Check the app developer section for migration details.
2. CocoaPods Enters Maintenance Mode—Final Shutdown in 2026
After December 2, 2026, the CocoaPods registry will become permanently read-only. While existing builds that depend on CocoaPods will still function, no new versions or pods will be added to the trunk after that date. This is a clear signal that Apple’s ecosystem is moving away from CocoaPods entirely. Flutter's decision aligns with Apple's direction and ensures that your apps can continue receiving dependency updates from the Swift package ecosystem. If your app relies on any CocoaPods-only plugins, now is the time to plan their migration or find alternatives.
3. No More Ruby Headaches for Dependency Management
One of the biggest wins for Flutter developers is the elimination of Ruby and CocoaPods from the typical setup process. Developers working on iOS and macOS apps often had to tweak Ruby versions, install CocoaPods via gem, and deal with conflicting installations. SwiftPM is natively supported by Xcode, so there’s nothing extra to install. This reduces friction when onboarding new team members and simplifies CI/CD pipelines. It also means fewer environment-specific errors, letting you focus on building features rather than debugging dependency infrastructure.
4. App Developers: CLI Handles the Migration Automatically
For app developers, the transition is largely painless. When you build or run your iOS or macOS app using the Flutter CLI, it automatically updates your Xcode project to use SwiftPM. You don’t need to manually modify project files or run migration scripts. However, it’s still wise to review the official Flutter migration docs for app developers to understand any edge cases. The CLI will also notify you if any of your dependencies haven't switched yet—see item 5 for how to handle that.
5. Fallback to CocoaPods for Non-Migrated Plugins (Temporarily)
If your app depends on plugins that haven’t adopted SwiftPM, Flutter won’t leave you stranded—yet. During the transition period, Flutter will automatically fall back to CocoaPods for those specific plugins. A warning will list exactly which dependencies are unsupported. This temporary fallback allows you to continue building while you push for updates from plugin maintainers. But note: CocoaPods support will eventually be removed entirely, so see plugin developer responsibilities for more on how to encourage migration.
6. Unsupported Plugins Trigger Clear Warnings
When you run or build your app, Flutter now prints a warning if any of your plugins lack SwiftPM support. The warning lists the offending dependencies by name, making it easy to track which packages need attention. This transparency helps you prioritize which plugins to replace or request updates for. If a critical plugin breaks your build due to lack of SwiftPM support, the recommended action is to file an issue with the dependency’s maintainer or search for an alternative package that already supports the new system.
7. Opting Out Is Still Possible (But Not Forever)
If SwiftPM causes a breaking issue in your project—perhaps due to a plugin that hasn’t migrated yet—you can temporarily disable it. Open your pubspec.yaml file, navigate to the flutter section, and add the following under the config block:
flutter:
config:
enable-swift-package-manager: falseThis reverts to CocoaPods for the entire project. If you choose this route, please file a bug report using the Flutter GitHub issue template. Include error details, your list of plugins and versions, and copies of your Xcode project files. This helps the Flutter team resolve issues before CocoaPods is completely removed.
8. Plugin Developers Must Add SwiftPM Support—Or Lose Visibility
For plugin authors maintaining iOS or macOS packages, this is a mandatory update. As of now, 61% of the top 100 iOS plugins have migrated. Flutter is incentivizing the rest by lowering the pub.dev scores for packages without SwiftPM support. To add support, create a Package.swift file and organize your source files according to the standard Swift package structure. If you already migrated during the 2025 pilot, there’s one extra step: you must add FlutterFramework as a dependency in your Package.swift file. Full documentation is available in the Flutter migration docs.
9. 61% of Top iOS Plugins Already Migrated
The community is making progress. According to Flutter’s own data, 61% of the top 100 iOS plugins have already adopted SwiftPM. This shows that the migration is well underway and that many popular packages are ready for the new default. For the remaining 39%, plugin maintainers are encouraged to take action soon to avoid blocking app developers and to preserve their pub.dev scores. App developers should check their dependency list and consider opening issues or PRs for packages that haven’t migrated yet.
10. Lower pub.dev Scores for Non-Migrated Plugins
To push the remaining plugins across the finish line, Flutter has implemented a scoring penalty on pub.dev. Packages that lack SwiftPM support now receive lower scores, which affects discoverability and developer confidence. This is a gentle but firm nudge for plugin authors to prioritize the migration. The scoring system rewards packages that follow best practices, and SwiftPM support is now considered a key part of that. If you’re a plugin developer, adding SwiftPM support not only future-proofs your package but also improves its public standing.
The shift from CocoaPods to Swift Package Manager marks a significant step in Flutter’s evolution. For app developers, the transition is mostly automated, but staying aware of unsupported plugins and the temporary opt-out option will keep your builds smooth. For plugin developers, the message is clear: migrate now to maintain visibility and compatibility. With the deadline of December 2026 approaching, taking action today ensures you're ready for the future of Flutter on Apple platforms.