Flutter 3.41.9 continued the framework's multi-release push to move iOS and macOS plugin authors off CocoaPods and onto Swift Package Manager, publishing dedicated migration guides for both app developers and plugin authors well ahead of Flutter 3.44 making Swift Package Manager the outright default. CocoaPods has been the de facto standard dependency manager for iOS native code in Flutter plugins since the framework's earliest days, but Apple's own tooling ecosystem has been steadily consolidating around Swift Package Manager as its blessed first-party solution for years, and Flutter's transition is ultimately downstream of that broader Apple platform shift rather than a Flutter-specific architectural preference. The practical urgency here is concrete rather than aspirational: the CocoaPods registry itself is scheduled to become permanently read-only on December 2, 2026, meaning packages that haven't migrated by then won't be able to publish new versions through that channel at all. Flutter continuing to support CocoaPods in maintenance mode buys teams time, but plugin authors specifically are on a hard deadline that app developers consuming those plugins are not directly exposed to until their dependencies stop receiving updates. For teams maintaining Flutter plugins with native iOS code, this release's documentation push is the practical signal to prioritize the Swift Package Manager migration now, while there's still runway before the registry read-only cutoff, rather than waiting until CocoaPods publishing is no longer an option and migration becomes a forced, deadline-driven scramble.