SiriKit Is Deprecated — Is Your App Ready for the Switch to App Intents

Your iOS app does not need to crash to lose visibility. This fall, an app that still relies on SiriKit can continue to compile, launch, and work normally, while having limited visibility to the new Siri.

Apple formally deprecated SiriKit at WWDC 2026, and with iOS 27 expected in September, the shift toward App Intents is becoming increasingly relevant for iOS teams planning their next round of updates.

For product leaders, the important question is not when Apple will physically remove every SiriKit API. It is when users will stop reaching your product through Apple’s newest discovery and agentic AI experiences.

What Actually Happened at WWDC 2026

Apple formally deprecated SiriKit on June 9, 2026, during the Platforms State of the Union at WWDC 2026. The direction was more than clear: modern Siri and Apple Intelligence integrations are moving to App Intents.

Apple’s own documentation now describes SiriKit and legacy Intents frameworks as providing support for legacy systems, while App Intents are recommended for modern integration with Siri, Apple Intelligence, Shortcuts, Spotlight, and other similar system apps.

For iOS teams, this is more than another framework preference. Apple Intents development is becoming an important part of preparing apps for the way Apple understands app capabilities and surfaces them to users through system intelligence features.

The timing matters because iOS 27 is expected to reach the public in September 2026. Apple announced the fall release window at WWDC, with current expectations pointing to September.

The Real Deadline Isn’t 2028, It’s This Fall

The biggest mistake a product team can make is looking at the eventual SiriKit SDK removal and deciding there is plenty of time.

There is a two- to three-year window before SiriKit is expected to entirely disappear from the SDK, roughly 2028–2029. But that is the hard technical deadline, not the business deadline.

The more important change arrives with iOS 27. The practical deadline: treat mid-August 2026 as the point by which your App Intents readiness should already be in place.

App Store review is beginning to reflect readiness around this period, well before the public iOS 27 release. Waiting for the formal SDK removal means waiting until long after the competitive impact has already started.

Soft Deadline vs. Hard Deadline

The distinction is critical. Your team can technically postpone migration and still ship an app. But “the app still works” is not the same as “the app still participates in Apple’s next-generation distribution layer.”

What Happens to Apps That Don’t Migrate

The immediate risk is loss of reach rather than loss of functionality. Starting with iOS 27, apps that depend on SiriKit will not be available to the new Siri experience powered by Gemini.

They are not expected to suddenly crash or stop opening. Instead, they simply stop receiving the new class of voice-driven requests that App Intents enable. That creates several business consequences.

• Less voice-driven traffic. A user can ask Siri to complete a task, but your SiriKit-based capability is no longer part of the path the new assistant uses to fulfill that request.
• Weak discoverability in Spotlight. Apple is expanding semantic indexing around App Entities and App Schemas so that app content can be understood by meaning, rather than only by exact keywords.
• Less participation in Apple Intelligence experiences. App Intents and App Schemas give Apple Intelligence structured knowledge about an app’s entities and actions. Without that layer, your product has less opportunity to be surfaced when the user expresses an intent.
• Fewer cross-app agent scenarios. Apple’s new approach is designed to let actions and content move across applications. A user’s request may involve multiple apps, with one action producing information that another app can use. Apple’s WWDC 2026 App Intents session explicitly demonstrates cross-app actions and content transfer.

That last point changes the competitive equation. Imagine two competing services offer essentially the same feature. One has exposed its capabilities through App Intents and the other still depends on SiriKit. When an AI assistant chooses which service can complete the user’s request, only one of them is prepared to participate.

The competitor does not need a better app store listing. It simply needs to be available to the assistant when the user asks.

What’s New in App Intents 2.0

Apple’s App Intents evolution is not just a replacement project. iOS 27 expands what apps can do once they become understandable to Siri and Apple Intelligence. For business leaders, four additions are particularly relevant:

• Streaming responses. Long-running actions can provide progress and results as they become available rather than behaving like a single, isolated request. For products with complex operations, this can make AI-driven interactions more practical and responsive.
• Multi-turn conversational follow-ups. Siri can maintain a more natural interaction around an action instead of requiring the user to formulate every request perfectly in one sentence. That reduces friction for complex workflows.
• View Annotations. Siri can understand elements currently visible on screen. A user can refer to something like “this message” or “the third item” rather than describing it from scratch. Apple positions View Annotations as part of its onscreen-awareness capabilities.
• App Schemas. Schemas give Siri and Apple Intelligence a semantic model of common app entities and actions. This means apps can become understandable through meaning rather than relying on users to memorize predefined phrases.

Together, these changes point to a broader shift: the app is no longer only a user interface. It is becoming a set of capabilities that an AI assistant can discover, understand, and invoke.

Early Movers Are Already Live

Apple’s direction is also visible in the companies already demonstrating the target experience. Uber, Amazon, YouTube, WhatsApp, and AllTrails are among the early launch partners showing how established consumer products can participate in the new Siri and Apple Intelligence ecosystem.

The strategic lesson is more important than any individual feature: major apps are treating AI-agent accessibility as a product distribution opportunity, not simply as another API migration.

That is consistent with Apple’s broader App Intents strategy. App Intents can expose actions through Siri, Shortcuts, Spotlight, widgets, and other system experiences, while App Schemas make those actions more meaningful to Siri.

A Practical Timeline for Business Decision-Makers

You do not need to start with a technical migration plan. Start with a product decision.

1. Audit Your Current SiriKit Exposure

Identify where SiriKit is currently connected to your product and, more importantly, which customer journeys depend on those integrations.

Ask:

• Which actions can users currently trigger through Siri?
• Which of those actions matter commercially?
• Are any important discovery or workflow features dependent on legacy intents?
• Which capabilities would be valuable in an AI-assisted workflow?

The overall goal is to establish what is actually at risk, not simply count deprecated APIs.

2. Assess the Codebase and Migration Effort

The size of the migration depends heavily on the age and architecture of the application. A modern iOS product with a clean separation between business logic and its user interface may have a relatively contained migration.

An older application with accumulated technical debt, legacy Objective-C components, or tightly coupled SiriKit functionality may require more preparation.

Apple provides an official migration path for converting SiriKit intents to App Intents, including support for maintaining backward compatibility where required. This is where an engineering assessment can turn an uncertain deadline into a realistic budget and delivery estimate.

3. Plan Around the iOS 27 Release Cycle

Do not make September your project start date. The safer approach is to work backward from the iOS 27 release and leave time for implementation, testing, App Store submission, and fixes.

With the practical readiness window already underway in August, teams that have not started should prioritize the highest-value SiriKit journeys first.

4. Budget for External Support If Resources Are Limited

If your internal iOS team is already committed to the iOS 27 release, security work, product roadmap, or other platform migrations, SiriKit migration can quickly become competing priority number five.

An experienced external team can help with the initial audit, migration scope, implementation, and release preparation without forcing the product roadmap to stop.

Why This Is a Business Decision, Not Just an Engineering Task

SiriKit deprecation is easy to categorize as technical maintenance. That framing misses the larger change.

Apple is moving toward an environment where users increasingly describe what they want done, while Siri and Apple Intelligence determine which apps and actions can fulfill that intent. That makes App Intents part of a broader question of AI-agent readiness.

A travel app, for example, does not only need to let users search for a flight. It increasingly needs to make that capability understandable to an assistant. A commerce app does not only need a checkout flow.

It needs a way for an AI agent to understand what can be purchased and what actions are possible. A productivity app needs its content and actions to be discoverable in contexts where the user may never open the app first.

This is the shift from an app-centric model to an intent-centric one, and it is already becoming part of the mobile product roadmap.

Final Takeaway

SiriKit is deprecated, but the real urgency is not the eventual disappearance of its APIs. The business risk starts much sooner.

iOS 27 is expected this September. The practical App Intents readiness window has already arrived. And an app can remain perfectly functional while quietly losing access to the voice, search, and AI-driven experiences that increasingly determine how users discover services.

For product leaders, the right question is therefore not “When will Apple remove SiriKit?” It is: “How much customer reach are we willing to risk by waiting?”