Apple opened its Siri AI Developer Preview to all developers on November 3, 2026, through the iOS 27.3, iPadOS 27.3, macOS 27.3 and visionOS 27.3 betas. Developers can use App Intents to make their apps’ content and actions available to Siri’s personal-context understanding, onscreen awareness and natural-language capabilities, according to Apple’s announcement.
The immediate job is to build and test integrations, not announce general availability. Apple says the new capabilities will first ship to customers “in a few months,” with App Store submissions opening in the spring.
The bigger shift is broader access to Siri as an app interface. Developers can expose custom actions, describe skills that combine several actions, and make entities discoverable through Spotlight’s semantic index. Those capabilities still depend on deliberate integration work. Siri does not automatically gain access to everything an app contains.
What Is Available Now, and What Must Wait
Apple’s announcement separates developer access from customer release. That distinction matters for teams deciding whether this is a prototype opportunity or a feature they can put in their next public update.
| Stage | Availability described in the sources | Practical consequence |
|---|---|---|
| Developer Preview | Available from November 3 in the iOS 27.3, iPadOS 27.3, macOS 27.3 and visionOS 27.3 betas | Developers can start implementing and testing integrations |
| Test distribution | Development-signed builds and internal TestFlight testing, according to iClarified | Teams can evaluate internally, but external TestFlight distribution is excluded |
| App Store submissions | Apple says spring; iClarified identifies this as spring 2027 | Submission access is still ahead |
| Customer release | Apple says a few months, without an exact date | The announcement is not a public launch commitment for a specific day |
The testing restrictions come from iClarified’s report, which says the integrations cannot yet ship through external TestFlight testing or App Store releases. Apple’s announcement confirms the broader preview and release schedule.
A submission window is also different from a customer launch date. Apple has not supplied enough detail to turn those two milestones into a precise rollout calendar. I’d treat spring as a planning checkpoint, not a promised date when every eligible customer will receive an integration.
What Apps Can Expose Through App Intents
Apple describes three important pieces of the expanded integration:
- Custom actions: Developers can make app operations available to Siri, with Apple giving examples such as checking a delivery, booking a reservation and placing an order.
- Multi-action skills: Developers can teach Siri how to combine several actions into a single experience for more complex requests.
- Spotlight semantic entities: Siri can surface entities in Spotlight’s semantic index without limiting them to an existing schema.
App Intents is the integration mechanism connecting those app capabilities to Siri. In practical terms, developers must identify the content Siri should be able to find and the operations it should be able to request. Natural language becomes another way to invoke those exposed capabilities.
The Spotlight change addresses a different part of the problem from action execution. Finding a relevant item and doing something with it are separate jobs. Broader entity support can help Siri locate app content that does not fit a pre-existing schema; an exposed action supplies something useful to do with that content.
That separation is worth preserving in development plans. An app with searchable entities but few useful actions may help Siri find information without completing the user’s task. An app with actions but poorly exposed content may leave Siri struggling to identify the item the user means. This is a design implication of the documented capabilities, not a measured result from the preview.
Skills Add Sequences, While Context Helps Identify the App
Skills are Apple’s mechanism for describing experiences that involve several actions. The announcement does not provide enough implementation detail to infer how reliably arbitrary workflows will execute, but it makes the intended expansion clear: developers can define more than isolated commands.
Context can also reduce how explicitly users need to identify an app. The Verge reports, citing Apple’s developer documentation, that users may omit an app’s name when it is in the foreground, has an active Live Activity, or is already the subject of a Siri conversation.
Its example involves a ride-hailing app: after requesting a ride and following its Live Activity, a user could ask Siri to change the pickup location without naming the app again.
For developers, that makes follow-up requests a useful evaluation target. A command that works when someone says the app’s name and every required detail may behave differently when the request depends on an ongoing activity. The supplied coverage contains no independent testing of recognition accuracy or task-completion reliability.
App Intents Remains an Explicit Access Boundary
iClarified reports that developers must explicitly expose content and actions through App Intents. Existing App Intents code can be adapted without adding a new entitlement or joining a separate developer program.
That is a meaningful distinction within the phrase “open to all developers.” Broader eligibility removes an access hurdle, but it does not remove the implementation work or make every existing app Siri-ready.
Consider a delivery app. Making an order available as an entity could help Siri identify which delivery a person means. Exposing a delivery-status action would give Siri a defined operation to request. Changing the delivery address would be another capability for the developer to expose and evaluate. This is an illustrative breakdown, not a published implementation recipe.
The explicit boundary is useful because it gives teams a concrete inventory to review: which content is discoverable, which actions are callable, and what each action can change. It should not be treated as proof that every privacy or authorization question is settled. Apple’s announcement does not spell out the complete permission, confirmation or production-policy model.
I’d begin with a narrow, easy-to-verify action such as checking status before attempting a workflow that places an order. The basis is straightforward: each additional action creates another outcome to validate, and a transaction has more consequential failure cases than returning information.
Device, Region and Usage Limits Still Apply
“All developers” describes access to the preview, not universal access for users. Apple’s availability notes impose several conditions:
- Hardware: Siri AI requires an Apple Intelligence-enabled device.
- Language: The device must use a supported language. Apple lists English, French, Japanese, Korean, Portuguese and Spanish.
- Planned languages: Traditional Chinese, Norwegian, Turkish and Vietnamese are described as coming soon.
- Region: Siri AI is currently unavailable in the EU on iOS, iPadOS and watchOS.
- Age: Siri AI is unavailable to users under 13.
- Feature coverage: Some features may vary by region or language.
Apple’s general Siri AI beta availability note also lists watchOS 27.3. Its opening list for this third-party Developer Preview names iOS, iPadOS, macOS and visionOS. Those lists should not be collapsed into a claim that the same developer integration preview is available on every listed platform.
Frequently Asked Questions
3 questions
1Can Developers Ship These Integrations Today?
No. The preview supports development builds and internal TestFlight testing. App Store submissions are scheduled to open in spring 2027, while Apple describes customer release only as a few months away.
