Apple Opens Siri AI Actions to Developers

“Check my delivery” sounds like one request. Underneath, an app has to define which delivery record the user means, what information can be surfaced and whether the next step is merely a status lookup or a change to the order. Apple’s new Siri developer preview makes those app-defined actions more accessible through natural language. That gives developers a new entry point—and puts more weight on the boundaries they design into it. ^{[1] [2]}

The app still defines what Siri can do

Apple says the preview allows apps to bring content and actions into Siri AI using App Intents. An app can describe a task—such as checking a delivery, booking a reservation or placing an order—so Siri can match a person’s request to an action the app has declared. The app remains responsible for implementing that action and returning its result. Siri supplies the conversational route into the capability; it does not automatically grant itself every permission inside the app. ^{[1] [3]}

For developers, that changes the design question from “How do I put a chat box in my app?” to “Which app actions are safe and useful to invoke from a conversational surface?” A delivery lookup can be read-only. A cancellation, payment or address change has consequences and may need a confirmation step inside the app. The action schema should make that difference clear, and the app should continue to enforce its own identity, authorization and validation rules.

Apple is also introducing skills for combining several actions. A user might ask for a restaurant reservation and then a reminder; a skill can coordinate app-defined steps into one experience. That can reduce navigation, but a multi-step request also creates more places for the system to misunderstand an entity, apply the wrong account or finish only part of a task. The app should report what happened and what still needs confirmation instead of treating a fluent reply as proof that every step succeeded.

This is an early developer window

The announcement describes a preview in beta releases of iOS 27.3, iPadOS 27.3, macOS 27.3 and visionOS 27.3. Apple says customer shipping is expected in a few months and App Store submissions will open in spring. It also says more detail about terms and usage policies will follow. In other words, developers can explore the interaction contract now, but should not treat preview behavior, policy or availability as settled. ^[1]

Availability is also not universal. Apple lists supported languages and says the experience is unavailable in the EU on iOS, iPadOS and watchOS, and to users under 13. Some server-side Apple Intelligence features have daily usage limits that vary by feature, request complexity, system demand and policy. A product plan built around this preview needs to account for those constraints and keep a usable in-app path for people who cannot access Siri AI.

What a useful integration needs

Teams can begin with a small, low-risk action set. Read-only actions—finding a saved item, checking an order or locating a document—are easier to test than actions that move money or change records. Each action should state which fields are required, what account context it uses, which outcomes need explicit confirmation and how the app handles partial failure. These rules are basic application design, but a conversational entry point makes them more visible because users may not see the usual screens before an action runs.

Testing should include more than the happy path. Try ambiguous names, missing details, multiple accounts, expired sessions, unsupported languages and retries after a slow response. For a multi-action skill, verify that a failed second step does not leave the user with an inaccurate “done” message. Preserve the app’s own permission checks even if Siri has access to personal context or what is on screen; contextual understanding is not the same as permission to disclose or change app data.

Apple’s opening also comes with a platform tradeoff. App Intents can make a service easier to reach from across Apple’s operating systems, but teams are building for Apple’s preview, submission rules and eventual policies. Developers should avoid promising that a preview integration is broadly available or treating Siri as the only route to a core feature.

Readers can compare this developer opening with the earlier public beta of Apple’s rebuilt Siri and the debate around platform changes and app work. The next meaningful milestone is not another demo; it is the customer release, with clear permission behavior, supported-device coverage and stable policy for third-party actions.