Siri AI opens to every app: what to do with App Intents

· 7 min read

#apple-dev#ai

On November 3 Apple opened a Siri AI Developer Preview to every developer: with the 27.3 betas, any app can hand Siri AI its own custom actions and content through App Intents. The catch is that it works only in development builds and TestFlight internal testing for now, so this is a window to prepare, not to ship.

In short

June to September 3 November
What Siri can reach in your app content and functions that fit system-defined schema domains custom actions and custom content too
Languages English at launch, five more announced for "next month" English, French, Japanese, Korean, Portuguese, Spanish; Turkish "coming soon", no date
Who can try your integration Siri AI developer testing began on the iOS 27, iPadOS 27, macOS 27 and visionOS 27 betas development-signed device builds and TestFlight internal testers; not external TestFlight, not the App Store
EU (iOS, iPadOS, watchOS) not available not available; Apple says it is looking for a way
First customer release not published App Store submission opens in the spring; customers a few months after the preview, no date

Then and now

The table above shows how far this step goes. Apple announced Siri AI in June, and it shipped as a beta in September. The June announcement talked about personal context and Spotlight and did not mention App Intents. This week's documentation does, and that is the new part.

I wrote about Siri AI in passing in Your iPhone widget can now show up on Apple HomeView, where the EU gap already showed up. It is still there.

Siri AI so far, from announcement to the App Store window Four boxes from left to right: June 8, developer testing; September 14, English-only beta; November 3, custom actions open in a preview; spring, App Store submissions open. Jun 8 developer testing Sep 14 English-only beta Nov 3 custom actions Spring submissions open
Siri AI so far: the June announcement, the September beta, this week's preview for custom actions, and the spring App Store window Apple mentions.

Custom actions with App Intents

Apple's documentation says Siri used to work mainly with data and functions that match system-defined app schema domains. Now it can also work with custom actions and custom information, but only what you expose through App Intents. There is no new entitlement and no separate program: you update the App Intents code you already have.

The mechanical part is small. Add the @AppIntent(.tool) macro to an existing or new App Intent, and it adds ToolIntent conformance. If the intent already fits a schema in a main domain, such as sendMessage in a messaging app, you do not add the macro. Where a schema is also supported by Shortcuts, you write @AppIntent(.tool, schema:), for example .tool, schema: .journal.createEntry. Siri tells intents apart by their title and description, and every @Property, @DeferredProperty and @ComputedProperty of an entity needs a description too.

To be found, an entity has to be in Spotlight: conform it to IndexedEntity and index it with indexAppEntities(_:priority:) on a named CSSearchableIndex. Apple says the default index is only for prototypes.

Privacy is your call. By default, entities do not ask for authentication before Shortcuts or Siri show them. For sensitive data, Apple's example is a bank account: IntentAuthenticationPolicy can require authentication, and visibility: .internal hides an app-only property from Siri and Shortcuts.

In some cases people do not have to say your app's name: your app in the foreground, a Live Activity running, or a Siri conversation that already mentioned it. Siri can also show your content in a card with your own views.

Skills for bigger jobs

A single tool intent does one thing. For multi-step jobs, Apple adds app skills: you add a Skills.skillsbundle to your project (one per target), and each skill is a folder with a SKILL.md inside. The frontmatter takes a name (1 to 64 characters, the same as the folder name) and a one-line description of up to 1,024 characters. The body is free text of up to 10,000 characters, and Siri reads it only after it has decided the skill fits the request.

Apple says skills use a subset of the Agent Skills format. My reading: it is the same folder-with-a-SKILL.md idea I wrote about in Agent Skills moves to a foundation. A skill is just a folder, cut down. Other frontmatter fields and support files such as scripts are not supported. And a skill does not force behaviour: Siri does not run the tool intents you list in order, the skill only gives it more to go on.

The good and the not-so-good

Good:

Not so good:

My take, not fact: since Siri finds only what you offer, small and clearly named actions look like the safest start.

What I would do

My suggestions, not facts:

  1. Install the 27.3 betas and Xcode 27.3 beta on a real device. Apple says to validate skills on a device, not in Simulator.
  2. Pick one or two actions people would actually ask for, and turn them into App Intents with a clear title and description.
  3. Put the entities behind them in Spotlight with IndexedEntity.
  4. Decide what is sensitive: add an authentication policy, or mark app-only properties visibility: .internal.
  5. Run Siri Integration Advisor and Siri Evaluations before you touch anything else.
  6. Write a skill only when a job really takes several steps.
  7. Do not promise this to users yet: it is not in App Store builds.

Apple lists a Group Lab with its engineers on November 5 if you want to ask questions.

Sources