The question nobody at Apple answers

In September 2017, iOS 11 shipped with a quiet typography decision: Urdu text would render in Nastaliq by default . For a billion devices, the hanging cascade stopped being a font you installed and became something the platform just does .

Apple, characteristically, did not issue a press release naming the typeface. Ask around and you will hear confident guesses — "it's Noto, obviously" or "it's custom" — and very little evidence. So we treated it the way we treat every Nastaliq claim: as an open question with a findable answer.

The forensic trail

The answer was sitting in the platform's own plumbing:

1. The shaping signature. Whatever ships must cascade Urdu through cursive attachment — the character-based approach we explain in the ligature-vs-character explainer. That immediately rules out every ligature-library face. 2. The CoreText fallback chain. Mozilla's font fallback data for Apple platforms lists the system's Urdu cascade explicitly — and it points to a UI variant of Noto Nastaliq Urdu . 3. The binary itself. The font carries version 13.0d1e2 and 1,133 glyphs — one glyph shy of the 1,134 in the contemporary catalogue release, the kind of delta a UI-tuned cut produces (tightened verticals for system UI metrics).

So: the iPhone's Urdu voice is Noto Nastaliq Urdu UI — a variant that, as far as the public record shows, has never been released through the Noto fonts project . You cannot download the exact font in your pocket.

Why that answer matters more than the trivia

If you build for Apple platforms, you are designing against a font you cannot install. The practical consequences:

• Testing on macOS ≠ testing on iOS. Match the OS version, not the family name. • Line-height budgets differ. The UI cut is tuned for system metrics; your web Nastaliq CSS should not assume the catalogue cut's boxes. • Screenshot-driven identification now works. This is exactly the case our visual font search was built for: paste an iOS Urdu screenshot, find the family.

The bigger picture: platforms as foundries

Apple is one branch of a quiet pattern. Google commissions and open-sources: Noto Nastaliq Urdu (designed with Monotype, maintained by the notofonts project) and Gulzar (Borna Izadpanah's Type Directors Club-awarded design) both began as platform bets. Microsoft shipped Urdu Typesetting with Windows 8 in 2012 — a system-level Nastaliq whose designers remain officially uncredited on Microsoft's own typography page, an invisibility we document in its archive record.

We now track the platform-shipped Nastaliq families as first-class records — including the Noto Nastaliq Urdu UI entry, with its version, glyph count and evidence trail.

Check it yourself

Open any Urdu text on an iPhone. That cascade is Noto's design language, tuned by Apple, maintained by nobody you can email. Then open Noto Nastaliq Urdu here, type your own text, and compare — the differences are subtle until you know to look, then impossible to unsee.

The full evidence chain — sources, grades, the CoreText listing — lives in the Nastaliq Research Archive. Next in the series: the national font nobody can date.

Identification based on system-font forensics recorded in the rtlfonts.com Nastaliq Research Archive (database v1.4.0).