Apple has opened App Store submissions for iOS 27 apps built with Xcode 27. The Foundation Models framework lets UAE developers add on-device and cloud AI, but Arabic support needs careful testing.
Apple opened App Store submissions for iOS 27 apps on September 9, 2026. Developers can build with the Xcode 27 Release Candidate, test through TestFlight and submit updates that use Apple Intelligence, the Foundation Models framework and other iOS 27 features. From April 2027, new App Store uploads must use the iOS 27 SDK or later and target iOS 15 or later. (developer.apple.com)
For a UAE app business, the practical change is not that every app needs AI. It is that Apple now offers a native route to add language features inside an iPhone app, with choices between on-device models, Private Cloud Compute and other model providers. The sensible first step is to test one useful workflow, not rebuild the whole product.
iOS 27 makes AI a platform capability, not just a separate chatbot feature.
Foundation Models is a native Swift API. It can use Apple’s on-device model, Private Cloud Compute or another provider that conforms to Apple’s Language Model protocol. Apple lists summarisation, entity extraction, text refinement, image understanding, structured output and tool calling among the supported patterns. The Vision framework can provide tools such as OCR and barcode reading for image-based tasks. (developer.apple.com)
That gives a UAE retailer, property company or service business a way to add features such as summarising customer notes, extracting information from a document, classifying an enquiry or helping staff search structured records. On-device processing can also support features that work without an internet connection, although the app owner still needs to decide what data is sent to a cloud model and how that data is handled.
Apple also supports Dynamic Profiles, which let developers change the model, tools and instructions during a continuing session. That is useful where one screen needs to answer a simple question locally, then call a larger model or an approved business system for a more complex task. (developer.apple.com)
The opportunity needs a qualification. Apple’s Foundation Models documentation says the on-device model understands and generates text in languages supported by Apple Intelligence. Apple’s published Apple Intelligence language list for iOS 27 does not include Arabic. Arabic is listed as a system language, but that is not the same as saying Apple’s built-in generative model supports Arabic. (developer.apple.com)
A UAE developer should therefore treat Arabic output as a test requirement, not an assumed capability. A bilingual app may need a separate model provider, a model brought into the app through Core AI, or a server-based model that supports the required Arabic variety. Apple’s framework is designed to expose other providers through the same general API, so the interface can remain consistent while the model choice changes. (developer.apple.com)
A worked example would be a Dubai delivery app that receives Arabic and English customer notes. The first version could extract order numbers and delivery areas on supported devices. The team would then test Arabic accuracy, mixed-language messages, Gulf vocabulary and failure cases. If the built-in model is not suitable, the app could route that task to a supported external or custom model instead of pretending that on-device Apple Intelligence solves it.
The immediate submission window is open, but the more useful planning date is April 2027. From then, iOS and iPadOS apps uploaded to App Store Connect must be built with the iOS 27 SDK or later and target iOS 15 or later. Existing apps do not need to adopt Foundation Models simply because the framework exists, but they do need a compatible build process before the requirement takes effect. (developer.apple.com)
A sensible UAE app team should:
The framework also brings model change into the testing plan. Apple notes that the on-device model can change when users update their operating system, so prompts and outputs should be tested again rather than treated as permanently stable. (developer.apple.com)
If your business already has an iPhone app, ask the development team for one small proof of value: a summary, extractor, classifier or search assistant tied to a real workflow. Measure accuracy and staff time saved before adding a wider AI layer. If you do not have an app, there is no reason to create one merely because Foundation Models exists. A website, ERP workflow or WhatsApp process may still be the simpler route; Paknology also handles websites and mobile apps and ERP and automation where those are the better fit.
Paknology has a commercial interest where this leads to an app build, an automation project or a website. We do not have a reason to recommend an iOS project where a simpler workflow will do. If an app is justified, prepare your current codebase, test devices, Arabic examples and data-handling requirements before asking for a build through Websites & Mobile Apps.
Sources
Book a free consultation and get a clear roadmap — from company formation to a fully automated digital operation.