WWDC 2026 took place this week, and Apple announced a lot. Most of it won’t change how Flutter teams work day to day. In this article we focus on the announcements most likely to have an impact on Flutter, ordered by what we expect to come up most often in client work over the next six months.
UISceneDelegate is now required on iOS 27
This is the biggest item for Flutter teams, and it lands as a confirmation rather than a surprise. Apple said at WWDC 2025 that any UIKit app built with the SDK after iOS 26 would need to adopt the UIScene lifecycle or it would no longer launch, and the iOS 27 SDK makes that real. The requirement is SDK-driven, not OS-driven: an app built against an older SDK still launches on iOS 27. The Flutter team has been preparing for this since Apple’s warning. Flutter 3.38 shipped UIScene support and flagged the upcoming requirement, and 3.41 made it the default with build-time auto-migration for projects with an unmodified AppDelegate. Apps on a recent Flutter version are covered. The work shows up in custom AppDelegates, older Flutter versions, and any iOS plugin still on the old scene lifecycle.
App Intents are the new front door to Siri
The new Siri performs systemwide actions through App Intents, so the assistant can only act on what an app exposes through that framework. SiriKit is now on a deprecation path, and Apple is directing new work to App Intents. There is no official App Intents integration in Flutter, neither a clear plan to create one yet (flutter/flutter #170589). Community packages on pub.dev offer early bindings, so we will see how they evolve.
Foundation Models opens up to third-party providers
Apple introduced a public LanguageModel protocol in the Foundation Models framework that puts the on-device Apple model and cloud models behind one Swift API. Anthropic and Google publish Swift packages for their models through it. The on-device model also gained image input and a Python SDK. For Flutter, this opens a platform surface for on-device summarization, classification, and rewriting without bundling a model, reached today through platform channels or FFI since there is no Dart binding yet. Flutter AI integration of this kind is moving from experiment to product, and generative UI work is a worked example.
Liquid Glass keeps evolving
Liquid Glass in iOS 27 adds a Settings slider that personalizes the effect from ultra-clear to fully tinted, answering readability feedback from last year. macOS 27 (“Golden Gate”) carries the same control. The Flutter team is reviewing how Cupertino should evolve, and community packages exist for teams that need the look today. We covered what the design shift means for Flutter teams when it first landed. For apps where iOS aesthetics matter to the brand, we weigh native platform views against the cost of an extra render path on a project-by-project basis.
Xcode 27 and the new minimums
The impact here lands mostly on CI. Xcode 27 is Apple Silicon only, so runners still building on Intel Macs need a plan before adopting the iOS 27 SDK. Xcode 27 also drives the proposal to raise Flutter’s iOS minimum version from 13 to 15. Worth handling in the same upgrade window: Firebase stops publishing new versions to CocoaPods in October 2026, with the registry going read-only that December, so Swift Package Manager becomes the path forward. For enterprise teams juggling these SDK changes in their release cadence, release pipelines should not take weeks.
Accessibility quietly got better
Apple continued expanding system accessibility in iOS 27, with improvements to VoiceOver and system dictation. Flutter apps inherit most of this automatically, and the benefits land hardest in apps with well-formed Semantics trees. Use the upgrade as a prompt for auditing Flutter accessibility with Semantics on custom-painted widgets, charts, and dashboards.
The takeaway
For most Flutter teams, WWDC 2026 comes down to upgrade work. Confirm the UIScene migration completed cleanly, and plan for the iOS minimum bump. iOS 13 and 14 barely register in active device share anymore, so that one can move quickly. App Intents deserves a closer look on apps where Siri reach is part of the product.
The bigger opportunity is on the AI side. Apple’s on-device models now sit behind a single API alongside cloud providers, and the most interesting Flutter work will come from wiring them into existing user flows. That on-device, multi-model direction is the work our AI-native Flutter engineering platform is built for.
