Apple's October 2026 App Store Changes: A Checklist for App Teams

Apple shipped a dense batch of App Store changes in the first three weeks of October 2026: new creative assets and an Asset Library in App Store Connect, a revised set of App Review Guidelines, an updated Developer Program License Agreement, and submissions for the new iPhone Duo. None of these is dramatic on its own, but together they change how you prepare a release. This post walks through what actually changed, which parts affect a normal app team, and the checklist we now use before pressing "Submit for Review".

What changed, at a glance

Here is the timeline, taken from Apple's developer news feed and the App Store Connect release notes:

The rest of this article goes through these one by one, roughly in order of how much work they create.

Creative assets: a new top slot on your product page

Until now, the product page was mostly icon, screenshots and app previews. With iOS 27 and iPadOS 27, Apple added creative assets: images or videos that can appear as the product page header, as your search result asset, and on in-app event cards. Apple's announcement frames them as a way to "highlight your brand, promote seasonal offerings, showcase new content". Unlike screenshots, they do not have to show the app in use.

The creative assets specifications are worth bookmarking, because the sizes are new:

A few details from the spec and the asset best practices page that are easy to miss:

• Images cannot have an alpha channel or transparency. Export flattened PNG or JPEG.
• Videos are muted by default and loop. In search results they cannot be unmuted at all, so the video has to work silently.
• Keep the focal point in the centre. The same asset is cropped differently across devices and orientations.
• If you skip the search result creative asset, the App Store falls back to your in-app events, app previews and screenshots, as before.
• Apple provides templates for Figma, Photoshop, Pixelmator and Sketch, including a "universal" template meant to serve both the header and the search result.

Creative assets also work on custom product pages and in product page optimization tests, so you can A/B test a header the same way you test screenshots.

The rules that come with them: Guideline 2.3.14

The October 16 guidelines add Guideline 2.3.14 specifically for creative assets. They must relate to your app's content, functionality or overall brand, follow the normal metadata rules, and be appropriate for all audiences. They must not include "references to other apps with an intent to mislead, unverifiable product claims, or specific or discounted pricing information."

The best practices page is more explicit. Do not include prices, discounts, website URLs or copyright symbols; do not claim awards you have not received; do not show other platforms or marketplaces; and do not add Apple badges such as Editors' Choice or App of the Day yourself. Assets must meet a 4+ age rating even if the app is rated higher, and games with violence must avoid gore and weapons pointed at a person or at the viewer.

In practice, the "50% off this weekend" banner many teams already use in ads cannot be reused as a header. Keep a separate, evergreen version for the App Store.

Asset Library and the preview tool

The second half of the October 5 update is workflow. The new Asset Library puts screenshots, app previews and creative assets for an app in one place, and, importantly, lets you submit creative assets for review on their own, independent of an app version. Apple's example is approving assets for a seasonal campaign ahead of time and switching them on when the campaign starts.

Two practical points:

• Access requires the Account Holder, Admin, App Manager or Marketing role. If a freelance designer or a client's marketing person handles store art, give them the Marketing role rather than Admin.
• Assets can also be uploaded through the App Store Connect API, which matters if you already automate screenshots with fastlane or a CI job.

The preview tool shows how the header, app name, description, screenshots and search asset will look on the product page and in search results, in Light and Dark Mode and across devices and orientations. Use it before every submission; it is the cheapest way to catch text that sits under the status bar or gets cropped on iPhone Duo.

Guideline 2.5.19 and why "hidden features" now matters more

The headline of the October 16 update was a crackdown on AI "nudification" apps and on apps that behave differently after approval. Apple's companion note calls this "bait-and-switch". Two changes matter for everyone, not only for bad actors.

Guideline 1.2 now explicitly covers apps that let users "create, generate, upload, share, or otherwise contribute content", and names nonconsensual intimate imagery, including imagery generated with AI tools, as something apps must proactively prevent and remove. As 9to5Mac reported, the new text adds that developers who fail to implement safeguards, or fail to fix violations after notice, may be considered in violation of the Developer Code of Conduct. If your app offers AI image generation, an avatar generator or any user upload, you need filtering, a report button and user blocking, and you should be able to describe them to App Review.

Guideline 2.5.19 is new as a standalone rule: "Don't include any hidden, dormant, or undocumented features in your app; your app's functionality should be clear to end users and App Review." It adds that attempting to hide undocumented features in the binary, "such as through code obfuscation or other methods", is grounds for removal and termination of the developer account. The sentence about hidden features previously lived inside Guideline 2.3.1(a), as TECHi's comparison of the old and new text notes; the obfuscation language is new.

Apple has not said that feature flags or remote configuration are banned, and we do not read the rule that way. Gradual rollouts, A/B tests and server-driven content are normal engineering. The risk is a feature that App Review cannot see or that is not described anywhere. Guideline 2.3.1(a) already requires that new features be "described with specificity in the Notes for Review section" and be "accessible for review". Our reading: if a flag can turn on something meaningfully new, describe it in the review notes, make it reachable with the demo account, and do not ship whole features that stay dark until after approval.

Smaller guideline edits

• 3.1.1(a): the bullet on the Music Streaming Services Entitlement is folded into the StoreKit External Purchase Link Entitlements bullet, and links may now point to "a permitted destination", with approved destinations varying by region.
• Section 5: apps that facilitate human trafficking or child exploitation will be removed and also blocked from alternative distribution.
• Apple says translations of the updated guidelines will follow within a month, so for now read the English text.

iPhone Duo: recompile, check layouts, plan screenshots

Apple says iPhone Duo goes on sale on October 23, 2026. Every app will run on it, but how well depends on the SDK. According to Apple's preparation guide:

• Built with the iOS 26 SDK or earlier: the app runs, but sits in the centre of the inner display with empty space around it.
• Built with the iOS 27 SDK: the app resizes to fill most of the inner display, but still avoids the status bar on the right edge.
• Built with the iOS 27.1 SDK or later: the app uses the full display, and toolbars and tab bars appear vertically below the status bar. Check that your layout copes with vertical bars before shipping.

The most common bug the guide calls out is sizing from UIScreen.main. On a folding device the window size changes mid-session, so use view.bounds or window.bounds (or GeometryReader / onGeometryChange in SwiftUI) and recompute layout in viewDidLayoutSubviews or viewWillTransition(to:with:), not once at launch. Apple also ships an app resizability skill for the Xcode coding assistant; you can ask it to "get my app ready for iPhone Duo", or export it for other coding agents with xcrun agent skills export. Apple notes it finds most issues, not all.

For cross-platform teams (Unity, Flutter, React Native), the same principle applies: anything that caches screen size at startup, or locks orientation on the assumption that phones are tall, deserves a test on the iPhone Duo simulator.

The deadline to note: from April 2027, apps submitted to App Store Connect must include iPhone Duo screenshots. You have time, but it is much easier to capture them while you are already testing layouts.

The license agreement: a small task with a big blocker

The October 13 license agreement update covers, among other things, security requirements, Group Purchases for multi-seat subscriptions and volume purchasing for Apple Business and Apple School Manager organizations. You may never use those features, but the Account Holder still has to sign in and accept the new terms. Until that happens, App Store Connect can block some actions. For client projects where the client owns the account, send them a reminder now instead of discovering it on release day.

Our pre-submission checklist for November

This is the list we are using for our own and our clients' apps:

1. Account: Account Holder has accepted the October 13 agreement.
2. Build: compiled with Xcode 27.1 or later; layouts checked on the iPhone Duo simulator in both folded and unfolded states, portrait and landscape.
3. Code: no remaining sizing from UIScreen.main; size-dependent layout recalculates on change.
4. Review notes: every new or flag-gated feature is described specifically, with steps and a working demo account (2.3.1(a), 2.5.19).
5. User content: if users can generate or upload images, filtering, reporting and blocking are in place and mentioned in the notes (1.2).
6. Store art: optional creative assets prepared at the right sizes, flattened, centred, with no prices, URLs or self-added Apple badges (2.3.14).
7. Preview: product page and search result checked in the App Store Connect preview tool, Light and Dark Mode.
8. Screenshots: majority still show the app in use, per Apple's 2.3.3 guidance; plan iPhone Duo screenshots before April 2027.

Our take

For a small studio, the most valuable change is not the new header; it is that creative assets can be approved ahead of time in the Asset Library. Seasonal updates (Christmas, Lunar New Year) used to mean bundling art with a binary and hoping both passed review in the same window. Now the art can be ready a month early.

The guideline changes are mostly aimed at abusive apps, but 2.5.19 raises the cost of sloppy review notes. Honest apps are often held up simply because a reviewer cannot reach a feature behind a login or a region flag. The fix is boring: write clear notes and give reviewers a path to every feature. With account termination now spelled out as a consequence of hidden functionality, it is worth the extra ten minutes.

iPhone Duo is the one item with real engineering work. If your app uses fixed layouts, start testing this week rather than in March.

Sources

• Apple Developer: Latest News
• Showcase your apps with new assets on the App Store
• Creative assets specifications
• App Store asset best practices and resources
• Manage your App Store assets
• App Review Guidelines
• Strengthening App Review Guidelines against nonconsensual intimate imagery and bait-and-switch apps
• Prepare and submit your apps for iPhone Duo and Three steps to make your app shine on iPhone Duo
• App Store Connect release notes
• 9to5Mac: Apple's new App Store rules crack down on AI nudification and 'bait-and-switch' apps
• TECHi: Apple's new App Store rules target AI nudify apps and 'bait-and-switch' features

Need help preparing an iOS release, adapting an app for iPhone Duo or getting through App Review? Lightning Studio builds and maintains mobile apps from Da Nang. Write to support@lightning-studio.org or see what we do.

---

Cover photo: Black smartphone in hand (Unsplash) by Dennis Cortés, CC0 1.0, via Wikimedia Commons (cropped).