SiriKit has carried Siri into third-party apps since iOS 10 in 2016. Today, 14 September 2026, iOS 27 reaches iPhones, and most iOS teams now have the same question: does their Siri integration code still have a future? Since WWDC26 in June, headlines have called SiriKit deprecated, dead or retired. Some reports promised compile-time warnings for every app still using it and a two-to-three-year removal clock. Apple’s own documentation tells a quieter and more specific story, and that difference matters when you set a roadmap.
This guide separates what Apple has published from what has been repeated about it. We read the SiriKit, Intents and App Intents reference pages directly and checked every deprecated intent against the version that retired it. We also searched the transcripts of Apple’s WWDC26 App Intents sessions and the Platforms State of the Union for the word “SiriKit”. Then we turned the findings into an audit, a migration plan and a readiness checklist you can use this week.
The short version: Apple now describes SiriKit as legacy support, iOS 27 deprecates five more of its intents, and every new Siri capability Apple showed this year is built on App Intents. If you want the consumer view of what Siri can now do, our guide to everything new you can do with Siri AI covers it. This article is for the people who have to ship the code.
Table of contents
- What “SiriKit Is Deprecated” Actually Means in iOS 27
- A Short History of Siri Integration on iOS
- SiriKit vs App Intents: How the Two Frameworks Differ
- What Still Works on iOS 27 Today
- The App Intents Toolkit Apple Shipped in June 2026
- How to Audit Your App’s Siri Footprint
- A Step-by-Step Plan to Migrate From SiriKit to App Intents
- A Readiness Checklist for Your App
- Risks, Costs and Timing of the Switch
- FAQ: SiriKit and App Intents
- References
What "SiriKit Is Deprecated" Actually Means in iOS 27
Three different things get bundled together as “the SiriKit deprecation”. One is a new legacy label in Apple’s documentation. Another is a short list of individual intents with real deprecation annotations. The third is a set of claims about warnings and removal dates that came from press coverage rather than from Apple. Only the first two appear in Apple’s documents.
The legacy note on Apple’s documentation pages
The SiriKit, Intents and IntentsUI overview pages now open with the same note: “SiriKit, Intents, and IntentsUI frameworks continue to provide legacy support for Shortcuts actions, widget configuration, and most existing Siri interactions. To implement modern support for these features and integrate your app with Apple Intelligence and Siri AI, use the App Intents framework.”
Read that carefully. It does not say the framework stops working. It says it keeps providing support, calls that support legacy, and names App Intents as the route for anything modern, including Siri AI, the new assistant rolling out in beta with iOS 27. For planning purposes, “legacy” is the word to hold on to. SiriKit is maintained for existing behaviour and is no longer where new behaviour lands.
What Apple’s API reference does not say
Apple’s developer documentation records deprecations as version metadata on each symbol. That metadata is generated from the same availability annotations in the SDK that make Xcode show deprecation warnings. On 14 September 2026 it showed no deprecation version for the SiriKit technology page, the Intents framework, the IntentsUI framework, the INIntent base class or the INExtension entry point. The core framework is labelled legacy in prose, but it is not annotated as deprecated.
That matters because several WWDC26 write-ups reported a formal deprecation notice for the whole framework. Tech Times wrote on 8 June that apps using SiriKit “will receive compile-time deprecation warnings in Xcode”. It added that developers have “roughly two to three years” before SiriKit-dependent features stop working. We found no Apple document that sets out that window.
The five intents iOS 27 deprecates
The annotated deprecations in iOS 27 are narrow. Five intents from the lists and notes domain carry a deprecation version of iOS 27.0 and watchOS 27.0: INAddTasksIntent, INCreateNoteIntent, INSearchForNotebookItemsIntent, INSetTaskAttributeIntent and INSnoozeTasksIntent. Each carries the same instruction: “Please adopt the Notes or Reminders AppSchema domain instead.”
If your app is a to-do list, a notes app or a task manager that lets people add tasks or create notes by voice through SiriKit, these are the calls that will surface as warnings when you build against the iOS 27 SDK. For most other apps, the iOS 27 change is the legacy label rather than a broken build.
Where the “two to three years” figure comes from
We could not trace the widely quoted migration window to Apple. It is not in Apple’s framework documentation, and it is not in Apple’s 8 June developer press release. We also searched the transcripts of the five WWDC26 App Intents sessions and the Platforms State of the Union, and none of them mentions SiriKit by name. Treat the window as a guess about Apple’s habits, not a date.
| What was widely reported | What Apple’s documents show (14 Sep 2026) |
|---|---|
| SiriKit is formally deprecated | All three frameworks are described as “legacy support”; no deprecation version on the frameworks or on INIntent |
| Every app using it gets compile-time warnings | Only individually deprecated intents are annotated; iOS 27 adds five to the list |
| Two to three years until removal | No removal date or support window published |
| SiriKit apps become invisible to Siri | Apple says it still supports “most existing Siri interactions” |
| App Intents is the way into Siri AI | Confirmed: Apple directs Apple Intelligence and Siri AI integration to App Intents |
None of this makes SiriKit a safe long-term bet. Apple calls the framework legacy, retires it piece by piece, and no longer mentions it in its developer sessions, so it is only heading one way. But the accurate framing changes the urgency. Leaving is a planned migration, not an emergency patch for launch day.
A Short History of Siri Integration on iOS
The current transition makes more sense against the ten years that came before it. Apple has narrowed the framework before, and it built a migration path into App Intents from the start.
2016: launch with fixed domains
SiriKit arrived with iOS 10 in 2016. It let apps plug into a set of predefined domains through an Intents app extension that the system launched to resolve and handle each request. Apple’s INExtension reference still lists those original families: VoIP calling, workouts, messaging, payments, photos, ride booking, CarPlay commands and restaurant reservations. If an action did not fit a domain, Siri could not reach it.
Custom intents followed with Siri Shortcuts. Developers described them in an Intent Definition file inside Xcode, and people could run them from Siri or the Shortcuts app. That flexibility is why so many apps adopted custom intents for ordering, logging and quick actions that never matched a standard domain.
2019 to 2021: the first retirements
Apple has retired intents before. iOS 13 deprecated the separate audio and video call intents in favour of a single INStartCallIntent. iOS 15 went much further. It marked 17 intents as “no longer available”, covering bill payments, money transfers, photo search and playback, visual codes, note appending, task lists, call history, radio stations and in-car settings. Each carried the advice: “You may define a custom intent instead.”
2022: App Intents arrives in iOS 16
App Intents shipped with iOS 16, macOS 13, watchOS 9 and tvOS 16 in 2022. It replaced definition files with Swift types. From the first release it included CustomIntentMigratedAppIntent, which Apple describes as “an interface for replacing a custom SiriKit intent that allows existing shortcuts and donations to continue working”. In other words, the migration path was designed into App Intents from the start.
2024 to 2026: schemas, Apple Intelligence and Siri AI
In June 2024 Apple added schemas that connect App Intents to Siri and Apple Intelligence. That same month, the SiriKit update log recorded that standard and custom intents would be “automatically available to enhanced action capabilities of Siri, powered by Apple Intelligence”. It is still the last entry in that log. In June 2026 App Intents gained app schema domains, Siri AI integration and a batch of new protocols. The SiriKit pages now carry the legacy note, which names Siri AI and so post-dates its June 2026 announcement.
The chart below counts every INIntent subclass that Apple’s reference marks as deprecated, grouped by the iOS version that deprecated it: 2 in iOS 13, 17 in iOS 15 and 5 in iOS 27, for 24 in total. Bar widths are each count divided by the largest, 17.
The pattern is worth noticing. Earlier retirements pointed developers to custom intents, another part of the same framework. The iOS 27 retirements point them out of SiriKit altogether, to App Intents schema domains.
SiriKit vs App Intents: How the Two Frameworks Differ
The move from SiriKit to App Intents is not a rename. The two frameworks model an action differently, run it differently and tell the system about it differently, and those differences decide how much of your code survives.
Definition files versus Swift code
SiriKit custom intents live in an Intent Definition file, which Xcode turns into generated classes. App Intents has no separate definition format. You declare an action as a Swift type that conforms to AppIntent, and “during compilation, the compiler generates information that Apple Intelligence, Siri, and other system features need to discover and use your intents”. The source code is the definition.
Extensions versus flexible execution targets
A typical legacy integration handles background requests in an Intents app extension, so shared logic has to move into a framework both targets can use. Apple’s Soup Chef sample does exactly that with a shared framework called SoupKit. App Intents types can live in the app, an app extension, a framework or a Swift package. In the 2027 releases, the allowedExecutionTargets property lets you say whether the main app, an App Intents extension or a widget extension may perform an intent.
Fixed domains versus schema domains
SiriKit standard intents cover the domains Apple chose in 2016 and later trimmed. App Intents replaces them with app schema domains: system-defined schemas that tell Apple Intelligence exactly what an intent, entity or enum means. An email app that conforms an intent to .mail.createDraft, for example, tells the system it can create a draft in that app. There are 23 domains today, and apps can adopt schemas from several at once. Siri still has to turn free-form speech into a structured request, which is a natural language processing problem, and schemas make the result far more predictable.
Resolve, confirm and handle versus perform()
SiriKit requests pass through separate resolve, confirm and handle steps. Apple’s own migration sample says: “The Perform method in AppIntents subsumes the resolve, confirm, and handle functionality that was required with custom Intents.” Parameters are resolved by the system, which can infer values “from the current conversation or by asking someone explicitly”, and your perform() method runs the action and returns the result.
| Area | SiriKit | App Intents |
|---|---|---|
| Introduced | iOS 10 (2016) | iOS 16 (2022) |
| How actions are declared | Standard intents or an Intent Definition file | Swift types conforming to AppIntent |
| Where code runs | The app or an Intents app extension | App, App Intents extension or widget extension |
| Request lifecycle | Resolve, confirm, handle | perform(), with system parameter resolution |
| Your data types | Parameters in the definition file | AppEntity, AppEnum and TransientAppEntity |
| Custom UI | IntentsUI extension | Snippets returned from the intent |
| Apple Intelligence and Siri AI | Legacy support only | App schema domains and new 2027-release APIs |
| Documentation status | Legacy; last update log entry June 2024 | Actively extended; 15 listed changes in June 2026 |
What Still Works on iOS 27 Today
Before planning a migration, be precise about what is not broken. Apple’s legacy note lists three things the framework still supports, and existing users rely on all of them.
Most existing Siri interactions
Apple says SiriKit continues to support “most existing Siri interactions”. A messaging, calling or workout app built on standard intents should keep responding to the requests it handled on iOS 26, apart from the five task and note intents deprecated in iOS 27. The word “most” is Apple’s, and it is a reason to test your own flows on iOS 27 rather than assume.
Shortcuts actions and widget configuration
Custom intents defined for SiriKit still appear as Shortcuts actions, and widgets configured through those intents still work. Those are the other two items in the legacy note. People who built personal automations around your existing actions will not lose them today. They will lose them if you remove the intents carelessly, which is why CustomIntentMigratedAppIntent exists.
What the legacy framework cannot give you: Siri AI
Siri AI rolls out in beta with iOS 27 for supported devices set to English, with French, Japanese, Korean, Portuguese and Spanish due in October. Apple’s 8 June press release says App Intents updates “enable developers to connect their apps to Siri AI capabilities like personal context understanding, app actions, and onscreen awareness”. Apple’s current documentation points that work to App Intents.
The older 2024 note about legacy intents reaching Apple Intelligence has not been withdrawn. But nothing Apple published in 2026 says SiriKit takes part in Siri AI’s personal context, onscreen awareness or app toolbox. German outlet heise reported on 7 July that Apple is retiring SiriKit alongside the Siri overhaul, and that in beta 3 Siri AI could already read information from third-party apps such as Tessie and Ford’s own app.
Availability also shapes the decision. Apple’s feature availability page lists Siri AI as “Available in English” and “Not available in the China mainland and the European Union”. If much of your audience sits outside that footprint, existing Siri behaviour will matter to them for longer, so plan to run both paths for a while. For the wider picture of how assistants reach apps, see our analysis of whether your mobile app is ready for AI agents.
The App Intents Toolkit Apple Shipped in June 2026
The case for leaving SiriKit rests on what App Intents now offers. Apple’s App Intents update log lists 15 changes for June 2026 across four areas, and the app schema domains carry most of the Siri AI weight.
App schema domains: 23 ways to describe your app
Apple groups its schemas into 12 primary domains, 2 single-purpose domains and 9 Shortcuts-specific domains. The primary domains are Audio, Calendar, Camera, Clock, Mail, Maps, Messages, Notes, Phone, Photos, Reminders, and System and in-app search. The single-purpose domains are Assistant and Visual intelligence. The Shortcuts-specific set covers books, browsers, files, journaling, presentations, readers, spreadsheets, whiteboards and word processors.
Three primary domains are all-or-nothing. Apple’s guidance says Mail, Clock and Messages “require that your app supports every schema in the group”, and Xcode tells you at build time when a schema is missing. To start one, type the domain name and an underscore in Xcode, such as photos_, and pick a schema from the suggestions to get a template struct.
The chart counts the action schemas listed on each primary domain’s documentation page on 14 September 2026, 96 across the 12 domains. Bar widths are each count divided by the largest, Photos at 28.
Two details stand out for teams planning the move. Notes and Reminders, the destinations Apple names for the five deprecated task and note intents, are among the smallest domains, so that part of a migration is compact. And schemas get deprecated too: Photos, Books, Browser and Journaling each list deprecated schemas, so moving to App Intents does not end maintenance.
Entities that sync, own and suggest
Three new entity features target Apple Intelligence directly. SyncableEntity marks identifiers that stay stable across devices, so people can continue a task elsewhere. OwnershipProvidingEntity lets you prompt for confirmation before destructive or sensitive actions on shared or public entities. RelevantEntities lets Apple Intelligence suggest media entities, such as songs, during workouts and similar moments.
Intents that run longer, cancel cleanly and undo
The intent protocols fix long-standing gaps. LongRunningIntent extends background runtime and reports progress. CancellableIntent handles clean-up, and IntentCancellationReason separates a deliberate cancel from a timeout. UndoableIntent reverses an action. supportedModes sets foreground, background or both, and RunSystemShortcutIntent lets interactive widgets run shortcuts or open another app.
Testing with AppIntentsTesting
WWDC26 also introduced AppIntentsTesting, a framework Apple describes as validating your App Intents “through the same infrastructure used by Siri, Shortcuts, and Spotlight”. SiriKit had nothing comparable, and teams testing it usually relied on devices and manual voice runs. For a migration, it means you can write regression tests for each converted intent before you delete the old version.
| June 2026 addition | Area | Why it matters for a migration |
|---|---|---|
| App schema conformance | Apple Intelligence | The replacement for SiriKit standard intent domains |
| SyncableEntity | Apple Intelligence | Lets a request started on one device continue on another |
| OwnershipProvidingEntity | Apple Intelligence | Confirmation before risky actions on shared content |
| LongRunningIntent | App intents | Longer background work with progress reporting |
| CancellableIntent and UndoableIntent | App intents | Built-in cancellation clean-up and undo |
| allowedExecutionTargets | App intents | Explicit choice of app, extension or widget process |
| EntityCollection | App entities | Large catalogues without resolving every item up front |
| IndexedEntityQuery | App entities | Entities fetched from the Spotlight index by identifier |
| AppIntentError init(description:) | Errors | Readable failure messages instead of generic response codes |
Grouped by area, the 15 changes in Apple’s June 2026 App Intents update log break down as shown. Bar widths are each count divided by the largest group, 6.
How to Audit Your App's Siri Footprint
You cannot plan a migration until you know what you have. In older codebases the integration is often spread across targets, and the engineer who added it may have left. A focused audit usually takes a day and removes most of the guesswork.
Find every Siri touchpoint in the project
Search the whole workspace, including extensions, frameworks and Swift packages, for these markers:
import Intentsandimport IntentsUIin any source file.intentdefinitionfiles, which hold your custom intents- Classes that subclass
INExtension, and Intents extension targets in the project INInteractiondonations andINVoiceShortcutCentercallsINUIAddVoiceShortcutButtonin settings or onboarding screensINVocabularyregistrations for custom terms- Any use of the five iOS 27 deprecated intents named earlier
Sort what you find into five buckets
Group every touchpoint into one of five buckets: standard intents, custom intents, donations and suggestions, custom vocabulary, and IntentsUI views. Each bucket has a different App Intents destination and a different risk. Custom intents with existing user shortcuts need the most care. IntentsUI views usually need the most rework, because snippets are built differently.
Put the five iOS 27 deprecations at the top
If any bucket contains INAddTasksIntent, INCreateNoteIntent, INSearchForNotebookItemsIntent, INSetTaskAttributeIntent or INSnoozeTasksIntent, move it to the top of the list. Those are the calls with real deprecation annotations in the current SDK. Apple has already named the replacement, the Notes or Reminders schema domain.
Record who depends on each intent
For each intent, note who uses it and how you know. Product analytics, support tickets and App Store reviews that mention Siri or Shortcuts are all evidence. An intent that powers a popular automation is a migration you must get right. An intent nobody has triggered in a year may be a candidate for retirement rather than conversion.
| Legacy piece | App Intents destination | Migration risk |
|---|---|---|
| Custom intent in an Intent Definition file | AppIntent adopting CustomIntentMigratedAppIntent | High if people have saved shortcuts |
| Task and note standard intents | Notes or Reminders schema domain | Medium; deprecated in iOS 27 |
| Other standard intents | Matching app schema domain, such as Messages or Phone | Medium; some domains require every schema |
| Intent parameters | AppEntity, AppEnum or TransientAppEntity with queries | Medium; data modelling work |
| Add to Siri buttons and suggested phrases | App Shortcuts through AppShortcutsProvider | Low |
| IntentsUI custom views | Snippets returned from perform() | Medium; UI rebuild |
A Step-by-Step Plan to Migrate From SiriKit to App Intents
Apple’s own migration sample, Soup Chef with App Intents, gives a clear order of work. The plan below follows that sample and adds the checks a production app needs.
Step 1: Convert intent definitions with Xcode
Open each Intent Definition file and use the “Convert to AppIntents” button. Apple’s sample explains that the new files each get “an autogenerated structure and implement the CustomIntentMigratedAppIntent protocol”. Commit the generated code before you edit it, so reviewers can see exactly what the converter produced and what you changed by hand.
Step 2: Rebuild parameters as entities and enums
In the Soup Chef sample, each parameter of the custom intent becomes an AppEntity structure. Fixed choices become an AppEnum, and values without a unique identifier become a TransientAppEntity. Write entity queries that reuse your existing data layer, and return suggestedEntities() for short pick lists. This is usually the largest block of engineering in the whole migration.
Step 3: Move resolve, confirm and handle into perform()
Delete the separate resolution and confirmation handlers as you move their logic into perform(). Validate inputs there, request confirmation where an action is destructive, and return a dialog or snippet as the result. Keep the old handler in place until the new intent passes its tests.
Step 4: Adopt a schema where a domain fits
Check whether each action matches a schema domain. A notes app should adopt Notes schemas, a messaging app Messages schemas, and so on. Apple warns: “Only apply schemas for actions and content that genuinely match the domain’s intended purpose.” Actions with no matching domain stay as plain app intents, which still work in Shortcuts and App Shortcuts.
Step 5: Add App Shortcuts phrases
Replace Add to Siri buttons with an AppShortcutsProvider that declares phrases people can say without setting anything up. Note Apple’s privacy wording: it “may extract anonymized App Shortcuts data such as localized phrases, display representation values, and the title and description of related intents” to train machine learning models. Review your phrases and titles with that in mind.
Step 6: Test with AppIntentsTesting and real devices
Write AppIntentsTesting cases for each converted intent, covering parameter resolution, errors and results. Then test on physical devices running iOS 27, with Siri AI on and off, in English and in at least one other supported language. Also run existing user shortcuts that used your old intents, to confirm the donation and shortcut continuity that CustomIntentMigratedAppIntent promises.
Step 7: Keep the old path until your users move
Do not delete SiriKit code on the day the App Intents version ships. Keep both paths while your minimum deployment target and your audience’s iOS versions catch up. Remove the old path only when analytics show the old path is idle, or when your minimum iOS version makes it unreachable.
A Readiness Checklist for Your App
Use these questions to decide where your app sits today. A “no” or “don’t know” is not a failure, but it should become a ticket.
Product and business questions
- Do we know which features people use through Siri, Shortcuts or widgets?
- Would a Siri AI user expect to ask for our app’s main action in natural language?
- Is a significant share of our audience outside Siri AI’s launch languages and regions?
- Have we budgeted for migration work in the next two releases?
Engineering questions
- Have we listed every Siri touchpoint, including extensions and packages?
- Do we use any of the five task and note intents deprecated in iOS 27?
- Are our core data types modelled as entities that queries can resolve?
- Can we test intents automatically, or only by speaking to a device?
- Who owns the Siri integration code today, and does that person still work here?
| Readiness level | What it looks like | Next action |
|---|---|---|
| Ready | App Intents in place, schemas adopted, SiriKit only as a fallback | Add AppIntentsTesting coverage and plan the removal |
| Partly ready | Some App Intents or App Shortcuts, core actions still in SiriKit | Convert the most-used intents next |
| Exposed | SiriKit only, including iOS 27 deprecated intents | Migrate the deprecated intents in the next release |
| Invisible | No SiriKit and no App Intents | Start with App Intents and one schema domain |
Risks, Costs and Timing of the Switch
The switch is a trade between two risks: waiting too long and moving too fast. Both are real, and the right answer depends on how much of your product runs through Siri today.
The risk of doing nothing
Staying on SiriKit alone does not break your app today, but it closes doors. Your actions stay out of the app schema domains Apple Intelligence draws on, out of Siri AI’s new capabilities, and out of every App Intents feature added from here on. Apple’s pattern with the old framework is steady narrowing. Each release that adds App Intents features makes a SiriKit-only app look older by comparison.
The risk of rushing
The opposite mistake is deleting old intents before their replacements are proven. People who built automations on your custom intents will notice broken shortcuts before you do. Convert with CustomIntentMigratedAppIntent, keep both paths for a release or two, and measure before you remove anything. We saw the same lesson in another platform switch, covered in our comparison of VSTO add-ins and Microsoft Office Add-ins.
Timing against Apple’s SDK calendar
Apple opened App Store submissions for iOS 27 on 9 September. Its current rule, in force since 28 April 2026, requires apps uploaded to App Store Connect to be built with Xcode 26 or later and an iOS 26 SDK. Apple has not announced when the iOS 27 SDK becomes mandatory. If it follows that April pattern, the SDK that annotates the five deprecated intents will be required within the next year.
A practical timeline for most teams is to audit this month and convert the deprecated and most-used intents in the next release. Adopt schemas and App Shortcuts in the release after that, then retire SiriKit once your minimum iOS version and analytics allow. If you need help scoping the work, our web and mobile development team can review a Siri integration and size the migration. For background on the assistant itself, see what Apple Siri is and how it works.
FAQ: SiriKit and App Intents
Is SiriKit officially deprecated?
Not as a whole, in the formal sense. Apple’s documentation calls SiriKit, Intents and IntentsUI “legacy support” and points new Apple Intelligence and Siri AI work to App Intents. The framework and its core classes carry no deprecation annotation. Individual intents are deprecated: 2 in iOS 13, 17 in iOS 15 and 5 more in iOS 27.
Will my SiriKit app stop working on iOS 27?
Apple says SiriKit continues to support Shortcuts actions, widget configuration and most existing Siri interactions. Apps that use the five task and note intents deprecated in iOS 27 should test those flows first. Everyone should test on iOS 27 rather than assume, because Apple’s wording is “most”, not “all”.
Will existing shortcuts break when we migrate?
They should not if you migrate properly. CustomIntentMigratedAppIntent exists so that “existing shortcuts and donations continue working” after you replace a custom SiriKit intent. Test real user shortcuts on devices before removing the old definitions.
Can Siri AI use my app if it only has SiriKit?
Apple’s 2026 guidance says to use App Intents to integrate with Apple Intelligence and Siri AI, and its June press release ties Siri AI’s app actions and onscreen awareness to App Intents. A June 2024 note about Apple Intelligence remains online, but no 2026 Apple document describes a SiriKit route into Siri AI.
Which iOS version does App Intents need?
App Intents is available from iOS 16, macOS 13, watchOS 9 and tvOS 16. Many of the June 2026 additions, including Siri AI integration and the new protocols, need the 2027 releases such as iOS 27. Check each API’s availability before raising your minimum deployment target.
How long does the migration take?
It depends on the number of custom intents, how well your data is modelled and how much custom Siri UI you built. An app with a handful of custom intents and clean data models is a small project. An app with many intents, IntentsUI views and extension-only logic is a multi-release programme. The audit above will tell you which one you have.
References
SiriKit — Apple Developer Documentation
Intents Framework — Apple Developer Documentation
IntentsUI Framework — Apple Developer Documentation
INAddTasksIntent — Apple Developer Documentation
SiriKit Updates — Apple Developer Documentation
App Intents Framework — Apple Developer Documentation
App Intents Updates — Apple Developer Documentation
App Schema Domains — Apple Developer Documentation
Making Actions and Content Discoverable by Apple Intelligence
CustomIntentMigratedAppIntent — Apple Developer Documentation
Soup Chef with App Intents: Migrating Custom Intents
AppShortcutsProvider — Apple Developer Documentation
Platforms State of the Union — WWDC26
Build Intelligent Siri Experiences with App Schemas — WWDC26
Explore Advanced App Intents Features for Siri and Apple Intelligence — WWDC26
Code-along: Make Your App Available to Siri — WWDC26
Discover New Capabilities in the App Intents Framework — WWDC26
Validate Your App Intents Adoption with AppIntentsTesting — WWDC26
Apple Accelerates App Development with New Intelligence Frameworks and Advanced Tools
Apple Debuts iPhone 18 Pro and iPhone 18 Pro Max
iOS Feature Availability — Apple
App Store Submissions Now Open for the Latest OS Releases
Upcoming Requirements — Apple Developer
Siri AI Talks to Third-Party Apps for the First Time — heise online
WWDC 2026: App Intents Replaces SiriKit as Gemini Siri Migration Clock Starts — Tech Times