The early-adopter bonus: why Apple rewards the apps that move first

Most of what Apple asks of app developers arrives in two stages. First it is new and optional, and a few teams try it. Months later it is what everyone does, and sometimes it becomes a rule. In between there is a stretch where doing the work earns something extra, and that extra disappears once everyone has done it. I call it the early-adopter bonus. October 2026 has two of them open at the same time, one inside the app and one on the App Store.

Apple published both on the same day. On October 5 its developer news ran "Prepare and submit your apps for iPhone Duo" next to "Showcase your apps with new assets on the App Store", and App Store Connect announced them together in one banner.

The same work, done sooner

Part of this month's work will not stay optional for long. From April 2027, Apple requires iPhone and iPad apps uploaded to App Store Connect to be built with the iOS 27 SDK or later, and every app or game submitted to include iPhone Duo screenshots. For most teams the question is when to do the iPhone Duo work, not whether. Doing it in October costs about what it would cost in March. Only October comes with a product launch attached.

The new store assets stay optional. The bonus there works differently. The work is small, an image or two, and what you get is looking different in search for as long as most apps do not.

Where the bonus comes from

The first source is Apple's editors. New hardware and new features need examples, and the App Store is where Apple shows them. The day before iPhone X went on sale in 2017, the App Store opened a "Great on iPhone X" section of apps already updated for the new screen. In 2024, Apple announced more than 600 apps built for Vision Pro the day before it shipped. Among its featuring criteria Apple lists innovation, which it defines as "new technologies that solve a unique problem". For iPhone Duo it is even more direct. Apple's preparation page tells developers to send a featuring nomination and to state in it that the app is optimized for iPhone Duo, including all device poses. Apple rarely spells it out that plainly.

The second is arithmetic. On an ordinary day your app competes with millions of others for attention. In the weeks after something new ships, the competition for anything about that new thing is the handful of apps that did it. In late October, the pool of candidates for an iPhone Duo story is small, and so is the pool of apps with a designed search results asset. Both pools will fill up. How fast, nobody can tell you.

The third is contrast. A search result stacks several apps on top of each other. If yours has a designed asset while the apps around it show screenshots, it stands out. On iPhone Duo's inner screen an app with black bars down both sides stands out too, for the wrong reason. This part of the bonus fades as the rest of the store catches up, and it can go negative, because a weak header next to plain screenshots is still a weak header.

What going first costs

Going early means working with less information. The iPhone Duo simulator is not the phone, and until October 23 nobody outside Apple has watched ordinary people use it. The creative assets have no published conversion data, and Apple has given no review time for standalone assets. New rules also get interpreted by App Review for the first time on somebody's submission, and that might be yours finding out what a 4+ rating means for a horror game's header.

So I would only go early where the downside is small. Four questions help sort it out:

1. Will it become required, or simply expected, anyway? Then going early costs nothing extra.
2. Can it be undone cheaply? A header can be swapped from the Asset Library in minutes. A rewritten navigation cannot.
3. Will your users see it? iPhone Duo matters most if your users are the kind of people who buy a $1,999 phone.
4. Does Apple have a reason to show it off? New hardware and new store features are what its editors write about.

For most apps that already have a business behind them, both of this month's moves pass all four.

This month in the app: iPhone Duo

iPhone Duo goes on sale October 23, with pre-orders from October 16. Your app runs on it as it is, but an app last built before the iOS 27 SDK keeps its iPhone shape on the 7.6-inch inner screen, with black bars on both sides. Rebuilt with Xcode 27.1, it gets the whole display, and standard toolbars and tab bars move into a column on the side. Since October 5, App Store Connect accepts apps built for it.

What optimized means in practice, the four levels of work, and ten questions to ask your developer are in iPhone Duo: is your iPhone or iPad app ready for Apple's first foldable? Since the same date, App Store Connect also takes iPhone Duo screenshots and app previews: 1398 × 2034 pixels for the outer display and 2007 × 2853 for the inner one, plus their landscape versions. They are the cheapest proof, for an editor or a buyer, that the app was actually updated.

The ideal date for a launch-day featuring nomination has passed. Apple asks for two to three weeks of notice, which put it around October 2. Send one anyway through Featuring Nominations in App Store Connect, and use the Helpful Details section to say the app is optimized for iPhone Duo and supports every pose. Launch week is the busiest week for this kind of story, and there will be others after it.

This month on the App Store: header and search results assets

Also since October 5, App Store Connect takes two new assets: a wide header at the top of your product page, and an asset that takes the place of your screenshots in search results. They are optional, they appear for people on iOS 27 and iPadOS 27 and later, and the new Asset Library can approve them without a new build. The specs, Apple's rules and a checklist are in Header and search results assets: a new step in App Store optimization.

The two moves fit together. App Store Connect's new preview tool shows your product page on iPhone Duo, header included, so you can check the new artwork on the device getting the launch coverage. And if you are shipping an iPhone Duo update anyway, that release is a natural one to attach the new assets to.

An October plan

Submitting early and holding the release is the safer way to hit a fixed date. I explain why in the piece on App Store review times.

Next time

Apple has already announced the next ones. Apple Pencil support on both iPhone Duo screens is due later this year. Subscription bundles and suites are due later this year in iOS 27, and the new creative assets are meant to reach Apple Ads campaigns too. Each will follow the same pattern: a few months when doing it is unusual, then a few when it is normal. My own rule is to start with the ones I would end up doing anyway.

Where I can help

I have built native iOS apps since 2008. If you want help deciding which of this month's two is worth it for your app, or someone to do the iPhone Duo work, book a Monday slot.