Apple announced a schedule on October 31 for initial Apple Intelligence features in China: developer testing from November 4 and public availability with iOS 27.3 in December. It identifies a partnership with Alibaba to support Qwen in selected experiences, including Siri, Writing Tools and Visual Intelligence.

This is an announced plan, not confirmation that the service is already active for all Chinese users. The initial package explicitly excludes next-generation Siri AI.

A regional package under a shared product name

Apple’s current support page continues to describe restrictions for devices purchased in mainland China, and for a particular combination of location and account region on devices purchased elsewhere. It separates future activation of a core feature set from access to newer capabilities.

The two pages do not establish contradictory availability: one describes the current state, while the other announces an upcoming change. Users need to compare dates and individual capabilities instead of assuming every reference to Apple Intelligence denotes an identical package everywhere.

Support requires an eligible device and supported language settings. The general documentation does not establish that every internationally available capability will appear in the Chinese package. We therefore do not transfer the entire global feature list into this regional announcement.

Qwen integration does not mean wholesale replacement

Our editorial assessment is that a system feature must be distinguished from an external model that can handle a particular request. A partner’s appearance in the interface does not, by itself, establish that it performs every operation behind that interface.

For example, help drafting text and a change in how an assistant is invoked are different product questions. Even if they appear within one menu, evaluating them requires separate tasks and observations. This explains how to read the integration; it does not claim knowledge of an unpublished internal architecture.

We do not identify a specific Qwen checkpoint, the location of every server or contractual conditions not established by the checked announcement. Nor do we infer all personal-data flows simply from the partner’s name.

What an actual test launch would establish

A useful check after the announced date would record the installed operating-system version, the device and its regional configuration. It would then observe a specific capability rather than report only that “AI works”. These are editorial criteria for a future check; we have not installed the developer build.

That distinction also matters when interpreting a user report. A result from one device and configuration can verify that particular experience, but it should not be expanded into a claim about every supported device or account.

For developers, the schedule provides a reason to plan checks of their own workflows. For consumers, it offers a more concrete timeframe without guaranteeing availability before either the test or the public release actually arrives.

The substantive development is an official regional rollout plan with a named model partner. Deployment success, response quality and practical scope can be assessed after real access becomes available, rather than inferred from the announcement alone.

Cover: conceptual AI illustration of an invented phone interface, not a screenshot or proof that the service has been activated.

Editorial check: 2026-11-01T09:38:54+02:00 (Europe/Sofia).