iOS 27 shipped this morning. The format everyone spent the summer preparing for did not ship with it.

This is not a complaint about Apple being late. Platforms slip, and a fall window has three months left in it. It is a point about where the constraint actually sits, because a lot of teams have spent August and September briefing designers against a date that was never the date. The App Store creative asset — the image or video that fills your product page header and your search results slot — is gated on App Store Connect, not on the operating system. App Store Connect has not opened that gate. Every Apple page that describes the format was still written in the future tense on launch day, and the one artefact that would prove otherwise, an API endpoint you could submit against, exists only for Apple Maps.

What follows is a documentation reading, not a rumour. Every claim below is anchored to an Apple page fetched on September 14, 2026, quoted verbatim, with the negative findings labelled as verified absences rather than assumptions. It includes a correction to something we published three days ago.

01What actually shipped on September 14

Start with the only hard commitment Apple has made in its own words. The iOS marketing page carries one sentence about availability: “iOS 27 available starting 9.14.” That is the whole of it. There is no “available now,” no “available today,” and no Apple Newsroom release announcing general availability — the September newsroom items are iPhone Duo, iPhone 18 Pro, AirPods 5 and a preview piece dated September 11 that references iOS 27 repeatedly and never states a release date.

Apple’s developer-side language is softer still. The September 9 post announcing that App Store submissions had opened says the operating systems “will soon be available to customers worldwide.” The developer releases feed, checked this morning, lists iOS 27.0 RC (build 24A435) dated September 9 as the newest iOS 27 build. There is no public-release entry on it.

Meanwhile Apple has publicly conceded that iOS 27 is shipping with features pending: MacRumors reported on September 11 that two of them — Messages suggestions and password fixing — would not be ready for Monday’s launch. That is the ordinary shape of a modern OS release. Things arrive in point updates. It is worth stating plainly because it makes the creative-asset situation unremarkable as engineering and very consequential as planning.

02The sentence that reads like a launch date

Here is the sentence that has been doing the work in almost every piece of coverage since June, from Apple’s asset best practices page:

“Creative assets appear across the App Store in iOS 27 and iPadOS 27 and later including your product page, in search results, and when your app is featured.”

Read it again with the emphasis on the verb. It says where an asset appears. It does not say when you can make one. It is a rendering statement — these are the surfaces on which an approved asset will be drawn, and the minimum OS on which those surfaces exist. It is entirely compatible with a world in which no asset has ever been approved, which is the world we are in this morning.

The companion sentence is the fallback, and Apple states it directly: “If you choose to not use a search result creative asset, your In-App Events, app previews, and screenshots will appear.” We have previously read that as a forcing function — the slot is filled for you if you do nothing. That reading still holds in principle. What has changed is that today it describes the universal state rather than a choice, because nobody has had the opportunity to choose. The fallback is not the failure mode yet. It is the only mode.

Against that, here is what Apple’s advertising help page says, still, on the day the OS ships: “Creative asset capabilities will be coming to App Store Connect and Apple Ads in the fall of 2026.” The page is headed “Coming soon.” The header has not come off.

03The shipping vehicle hasn’t shipped

The most useful check nobody seems to have run is the least glamorous one. Creative assets are submitted through App Store Connect. App Store Connect publishes dated release notes. So: what do they say?

Two entries exist for the relevant window. September 10: “Minor editorial fixes were made.” September 9: you can now upload apps built with Xcode 27 RC using the new SDKs, and the app preview and screenshot specifications for iPhone Duo, iPhone 18 Pro Max, iPhone 18 Pro, Apple Watch Ultra 4 and Apple Watch Series 12 have been added — with the note that support for uploading iPhone Duo assets “will be available later this year.”

What is absent from those notes, verified by loading the page rather than by inference: any mention of the Asset Library, creative assets, product page headers, search result assets, or the product page preview tool. Apple’s own September 9 developer post names that preview tool and marks it, in two words at the end of the paragraph, “Coming soon.”

This is the cleanest available evidence, and it cuts both ways honestly. Apple documents App Store Connect changes with dates, which makes their absence meaningful in a documentation estate where almost nothing else is dated. If the Asset Library had opened, this is the page it would have appeared on.

→ THE PROMISE THAT LAPSED

“More detailed resources and guidance will be available later this summer”

That sentence is still live on Apple’s WWDC26 App Store guide, alongside “Coming this fall,” which appears three times on the same page. Summer ended on September 22 by one convention and August 31 by another; either way the guidance a designer was told to wait for has not arrived, and the page that promised it carries no date, so nobody can cite when the promise was made. This is the documentation pattern we catalogued in our running file of Apple’s self-contradictions.

04The API tell: Maps has an asset pipeline, the App Store doesn’t

Documentation prose can be aspirational. API topic indexes are harder to fake, because an endpoint either has a reference page or it does not. So we pulled both published indexes.

Apple’s asset best practices page says, of submission: “you can submit your assets for approval using App Store Connect, either alongside a new app version, or in your Asset Library. You can also use the App Store Connect API.” That last sentence asserts an API path and names no endpoint. No asset-submission or asset-review-status endpoint could be located in the App Store Connect API documentation.

Now the interesting half. The Apple Ads Platform API — the replacement for Campaign Management API v5, which sunsets on January 26, 2027 — does have an Assets section. Its scope line reads: “Upload, query, retrieve, and delete Apple Maps creative assets.” The workflow guide it pairs with is titled “Advertising Your Business on Apple Maps.” Every concrete asset endpoint in that API is labelled Maps.

On the App Store side the same index offers App Eligibility (“look up rejection reasons for creatives”), Product Pages, and Creatives — and nothing that uploads an image. So the surface Apple launched in March 2026 with one ad per result, whose auction mechanics we documented when nobody else had read the page, has a working creative-asset pipeline. The surface that carries two ads per query and nearly 65% of App Store downloads does not.

0
App Store creative-asset endpoints in either published API index. The only asset upload, query, retrieve and delete endpoints Apple documents are scoped, in Apple’s own words, to Apple Maps.

One more thing from that index, worth recording because it answers a question we have been carrying for two runs: the Ad Rejection Reasons topic is still entirely product-page framed — AppAsset, ProductPageReason, ReasonLevel — with no creative-asset rejection path. The enumeration values themselves would not load across seven attempts, so whether an asset-specific code has been added is unverified rather than absent. Say the weaker thing.

05The second rulebook still does not exist

Apple has committed, in writing, to reviewing creative assets twice. App Store Connect approves the asset; then, per the Apple Ads help page, “Apple Ads will also need to review and approve your ad creative, according to guidelines we’ll share at a later date, before your ads can run on the App Store.”

Those guidelines do not exist. The Apple Advertising Policies they would sit beside were last updated on February 26, 2025 — eighteen months ago, and fifteen months before creative assets were announced — and the phrase “creative assets” is verified absent from them. Apple’s asset page nonetheless names those policies as one of the two rulebooks you should read before you start designing, alongside the App Review Guidelines, a dual-jurisdiction arrangement we think is a first for an App Store object.

The content rules that do exist are the ones published on August 5 and covered a day later: every asset must meet a 4+ age rating regardless of the app’s own rating, and pricing, discounts, URLs, copyright symbols, unverifiable award claims, competing-platform logos and self-applied Apple recognitions are all out. We took those seriously enough to write a whole piece on the 4+ ceiling and where an offer is supposed to go instead. None of it tells you what the second reviewer will want.

→ FREE 10-POINT AUDIT

Know what your search slot is actually earning

We open your Apple Ads account and read it against Apple’s current documentation, not last year’s: placement mix, impression share, keyword economics, and the baseline you will want on record before the creative asset surface changes underneath you. One hour with a senior strategist. No pitch.

Book my free audit →

06What we got wrong three days ago

On September 11 we published a piece arguing that creative assets ship on two clocks, that the organic surface is automatic and the paid surface is opt-in, and that from September 14 the slot is filled for every app on iOS 27, either from an asset you designed or from material Apple picks. The structural argument — two surfaces, two clocks, two reviews — we still think is right, and today’s evidence strengthens it. The dated claim was wrong.

Neither clock has struck. The organic surface has not opened because App Store Connect has not opened it, and the decision we characterised as “choose, or be chosen for” is not yet available to make. We had the mechanism right and the timing wrong, and we had it wrong because we read an Apple sentence about rendering as a sentence about availability — which is precisely the failure mode we spend most of our time warning other people about. The original piece is here; treat its September 14 framing as superseded by this one.

We will also flag a vendor disagreement rather than quietly winning it. A NeoAds post dated August 24 asserts the assets are live with iOS 27 and that the header is already editable in App Store Connect. That was written three weeks before the OS shipped, and it is contradicted by Apple’s own currently live language. We could find no corroboration. It may yet turn out to be early rather than wrong.

07The measurement hole that outlives the launch

Here is the part that does not get fixed by Apple opening the gate next month.

QuestionMulti-slot, March 2026Creative assets, fall 2026
Opt-in?No — automaticOrganic: no. Paid: yes
Announced date?Yes, Dec 17, 2025No — “fall 2026”
Reporting dimension?Two impression-share metrics addedNone
Diagnosable from Apple data?PartlyNo
Public benchmark exists?None, six months onNone possible yet

Apple Ads reporting was re-read this morning. It defines roughly 32 metrics and breaks out by campaign, ad group, keyword, search term, ad, device, audience refinement, date and country. There is no creative-asset dimension, no image dimension, no video dimension, no header dimension. The finest granularity is the ad, and the closest thing to creative-level reporting is the ad variation, which predates creative assets and refers to custom product pages.

Compare the multi-slot precedent. When Apple doubled search-results inventory it did at least add two position-adjacent impression-share metrics. For creative assets it has added nothing. And it has added nothing on top of a baseline that is already unmeasurable: every public Apple Ads benchmark still describes a one-ad-per-query auction, six months after that stopped being the auction anyone buys.

The practical consequence is that the creative-asset change, whenever it lands on the organic surface, will be an uncontrolled universal change to the thing sitting next to your ad, with no instrument pointed at it. That matters more on this channel than on any other, because App Store search is where declared intent is intercepted and the value per user is correspondingly high.

08What to do in the next four weeks

Five things, in order, none of which require the feature to exist.

Take the baseline now. Export search-results tap-through rate, conversion rate and cost per acquisition at keyword level for a clean four-week window ending today, and store it outside Apple. When the organic surface changes there will be no asset-level dimension to diagnose it with, and the only defence is a before that you took yourself. This is the same discipline that made the Apple Ads account audit worth doing before multi-slot, and almost nobody did it.

Brief designers on the template, not on a number. Apple publishes no pixel dimensions in text on the developer site — the only specs stated in prose are on the advertising site, and they are an aspect ratio and a duration: images and videos must use a 3:2 ratio, videos must run 5–30 seconds, are usable in search results ads only, and play without audio. Everything else lives inside downloadable Figma, Photoshop, Pixelmator and Sketch files. Note that Sketch appeared in that template list without announcement; Apple’s August 5 post named only the first three.

Design to the stricter rulebook. You have one published policy set and one promised one. Design to the 4+ ceiling and the commercial bans, and assume the unpublished Apple Ads guidelines are at least as tight, because a second reviewer that was never going to refuse anything would not need separate guidelines.

Do not restructure campaigns for a feature with no date. There is nothing to configure. Ad creative is still built from the metadata and assets already in App Store Connect, on all three of Apple’s placement pages, which still do not mention creative assets at all.

Re-check three pages weekly. The Apple Ads help page, for the day “Coming soon” comes off the header. The App Store Connect release notes, for the Asset Library. And the Platform API index, for an App Store asset endpoint. Those are the three places the change will actually become visible, and none of them will send you an email.

The gaps we are naming

Apple has published no ship date for creative assets beyond “fall 2026” on the advertising side and no availability statement at all on the developer side. No pixel dimensions exist in text anywhere; the aspect ratio and video duration are published on one website and not the other. The Apple Ads creative guidelines do not exist, the review they govern has no published turnaround and no appeal path — a gap we mapped in detail when Apple’s own enforcement data came out, in the piece on post-publication ad removal — and the Advertising Policies Apple names as a governing rulebook have not been reopened since February 2025. Whether an asset-specific rejection code exists is unverified, because the enumeration would not load. Reporting offers no asset-level dimension, so the organic change will not be diagnosable from Apple’s own data by anyone. And no one, anywhere, has reported seeing a creative asset live on an iOS 27 device — which is the finding, not the caveat.

One honest note on method. Several of the negative findings above are verified absences: the page loaded and the text is not in it. A few are not, and we have said which. Apple’s documentation servers refused a number of requests today, as they do most weeks, and the absence of dates and changelogs across this estate means the only version history that exists is the one third parties keep. That is a poor substitute for a changelog. It is currently the only one there is.