Apple opened the Siri AI Developer Preview to all developers on 3 November 2026. Through App Intents, an app can expose content and actions to Siri AI, allowing users to request tasks such as checking a delivery, making a reservation or placing an order.
Most companies serving Hungarian consumers should not fund a full implementation yet. Siri AI is currently unavailable in the EU on iOS, iPadOS and watchOS. Hungarian is absent from both the six supported languages and the four languages announced for the next expansion. A domestic Hungarian-language app therefore faces two separate access gates.
A limited engineering test can make sense for an export-facing app with non-EU users in English, French, Japanese, Korean, Portuguese or Spanish. Confine the work to two or three frequent actions and keep the test small.
What access did Apple give app developers?
The Developer Preview ships in the 27.3 betas.
The platform change matters because Siri AI can reach executable actions inside third-party apps. The examples include checking a delivery, booking a reservation and placing an order. The announcement also introduces skills, which it says can combine several actions into one experience for more complex requests.
The Apple Intelligence developer page explains that entity schemas can contribute app content to the Spotlight semantic index, while intent schemas make actions available through natural language. The documentation says developers do not need to define specific phrases or change code as Siri’s language understanding evolves.
The features are expected to reach customers in a few months, and App Store submission will open in spring.
Why are most Hungary-focused apps still blocked?
According to Apple’s announcement, Siri AI is currently unavailable in the EU on iOS, iPadOS and watchOS, while Hungarian is not a supported language.
The six current languages are English, French, Japanese, Korean, Portuguese and Spanish. The next announced additions are Traditional Chinese, Norwegian, Turkish and Vietnamese. Siri AI is also unavailable to users under 13.
This leaves an iPhone app serving Hungarian-speaking users in Hungary without a user-facing Siri AI benefit when the features first ship to customers. Resolving the EU restriction alone would not remove the language barrier. Adding Hungarian alone would not remove the current EU restriction.
Build a production business case for macOS or visionOS only after Apple confirms EU availability. The separate fleet decision is covered in the earlier guide to Siri AI on company iPhones and Macs in the EU.
Which buyer situation supports action today?
| Buyer situation | Decision now | Reason |
|---|---|---|
| The app mainly serves Hungarian-speaking iPhone users in the EU | Monitor the release and defer full development | Both EU iOS availability and Hungarian support are missing |
| The app has a material non-EU audience using a supported language | Run a narrow engineering test | The Developer Preview is open and App Store submission is due to open in spring |
| An app agency serves clients in supported non-EU markets | Build a reusable App Intents pattern | Region, language and device eligibility still need to be checked for every client |
| The business has no Apple app | Take no project action | App Intents exposes the content and actions of an existing app |
Source: Apple’s developer announcement dated 3 November 2026. Use the table to choose the next step based on users’ actual regions and configured languages.
If you are considering several AI features for your app, the generative AI integration page can help define a narrow pilot scope. Generative AI integration
Which workflow belongs in the first test?
Limit the first test to a frequent action whose successful completion is easy to determine. The announcement gives three practical starting points:
- checking an order or delivery status;
- finding or managing a reservation;
- starting a predefined ordering action.
During the test, measure whether Siri AI selects the intended action from users’ natural wording, identifies the correct entity and responds appropriately to incomplete requests. If you test a multistep skill, evaluate every component action as well as the overall request.
Compare the Siri AI route with how users complete the same task in the app today. Further investment is justified only if users complete the action more reliably or with fewer steps. Measure the baseline on the sequence currently used in the app.
App Intents also connects with Shortcuts and the Spotlight semantic index, so part of the engineering work may be reusable across other Apple surfaces. That does not establish business value for an EU deployment in Hungarian.
How should cost and usage constraints affect the budget?
Apple’s developer announcement says server-side Apple Intelligence features have daily usage limits, but the company does not quantify them. Detailed terms and usage policies will follow, and expanded access will be available for a fee in the future.
Separate the initial budget into process mapping, entity and intent schema design, implementation, device and language testing, and ongoing maintenance. Until Apple publishes the conditions, avoid contractual promises to customers and retain a direct in-app route for every critical customer journey.
Build a numerical business case once the paid-access price and usage limits are available. Until then, judge the pilot by engineering effort, task-completion rate and the number of interaction steps removed.
How should you prepare for the spring submission window?
- Segment the user base by region, device and configured language.
- Select two or three frequent actions with an unambiguous completion state.
- Build the smallest useful entity schema and intent schema for those actions.
- Test on an Apple Intelligence-enabled device in a supported language, using realistic user wording.
- Compare task completion through Siri AI with how users perform the same actions in the app today.
- Before App Store submission, repeat the region, language and device checks, then expand only after the test meets its success criteria.
For an app focused on Hungarian-speaking EU users, process mapping is enough for now. Full development can wait. If the company is choosing among several possible AI features, the AI use case evaluator can help assess the business value and implementation conditions before engineering starts.