Apple stops taking On-Demand Resources from new apps in early 2027. Build downloadable content on Background Assets
If your app is about to get downloadable lessons, levels, catalogues or offline manuals, the old Apple way of doing it now has an end date for newcomers. Building on the replacement from day one is cheaper than moving later.

Apple's November 12, 2026 App Store Connect release notes say that from early 2027 it will stop accepting uploads containing On-Demand Resources from new apps or apps that have never used the feature, and recommend Background Assets. Apple already marks the On-Demand Resources API deprecated as of iOS 27. If you're planning downloadable content, build on Background Assets now; if you already use On-Demand Resources, put the move on next year's roadmap.
The line in the release notes
Apple added one sentence to its App Store Connect release notes on November 12: starting in early 2027, App Store Connect will no longer accept uploads containing On-Demand Resources from new apps or apps that have never used the feature. Apple recommends migrating to Background Assets.
It's easy to read past. If you don't know what On-Demand Resources is, you probably assume it doesn't concern you. But if your app is about to grow downloadable content, it concerns you directly, and the decision is cheapest to make now, before anyone writes code.
Sequence of work
How On-Demand Resources is being wound down
- iOS 9
On-Demand Resources introduced for downloading tagged content when the app needs it.
- iOS 27
Apple's documentation marks the API deprecated: use Background Assets instead.
- Nov 12, 2026
App Store Connect release notes announce the upload cut-off for newcomers.
- Early 2027
No uploads with On-Demand Resources from new apps or apps that never used it.
What it is, in plain terms
Some apps don't ship everything at install. A language app downloads the next unit when you reach it. A game fetches new levels. A retailer's app pulls a large catalogue or 3D models only when someone opens that section. A field-service app keeps offline manuals for the equipment a technician actually services. For years, one Apple way to do this has been On-Demand Resources: you tag content during development, Apple hosts it with your app, and the app asks for it when needed.
Apple's documentation now marks that interface deprecated as of iOS 27, with a short instruction: use Background Assets instead. The November notice adds a practical gate on top. From early 2027, new apps, and existing apps that have never used On-Demand Resources, won't be able to upload builds that contain it.
A deprecated feature you haven't started using is the cheapest migration you'll ever do: you just don't start.
The argument: don't start on the old thing
If you're planning downloadable content, build it on Background Assets from the first day. A deprecated feature you haven't started using is the cheapest migration you'll ever do: you just don't start.
That sounds obvious, but it's easy to get wrong in practice. A developer who has used On-Demand Resources before may reach for it out of habit, or copy a pattern from an older project. Tutorials and examples online will keep describing it for years. And "early 2027" is vague enough that a project kicked off now, aiming for a spring launch, could sail straight into the cut-off with a build App Store Connect won't take. Put one sentence in the brief, "downloadable content uses Background Assets," and the question is settled.
There's also a reason to want the newer approach beyond avoiding a rejected upload. According to Apple's documentation, Background Assets lets you update downloadable content without submitting a new app build. You can host the content on your own servers or have Apple host it, with the managed option handling downloads, updates and compression. You group content into asset packs and say which ones must be on the device before first launch, which can be fetched quietly in the background, and which wait until the person actually needs them. Apple also includes a local mock server in Xcode for testing before release.
How the work moves
Which of three situations you're in
- Planning downloadable content
Start on Background Assets. Don't build anything on On-Demand Resources.
- Already using On-Demand Resources
Not blocked by this notice, but deprecated. Put the migration on next year's roadmap.
- Neither
Nothing to do now. Note it for the day someone asks for offline content.
- Not sure
Ask your developer whether the project has On-Demand Resources tags enabled.
If you already use On-Demand Resources
The November notice doesn't block you. It applies to new apps and apps that have never used the feature. But the interface is deprecated, which is Apple's way of saying where this goes next, and those deadlines tend to arrive with a few months' notice at the busiest point of somebody's year.
So treat it as a roadmap item for 2027, not an emergency. Apple's migration steps are short: turn off the "Enable On-Demand Resources" build setting at the project level and anywhere it was overridden, remove the tags, remove the code that requests tagged resources, then adopt Background Assets in their place. The work that takes time isn't those steps. It's deciding how your content should be grouped and when each group should download, and testing what a person sees on a slow connection.
A sensible order is to start with your smallest, least risky set of downloadable content, move it, ship it, and watch what happens before moving the rest. If your downloadable content changes often, the ability to update it without a new build may pay for the migration on its own.
Apple-hosted or your own servers
The hosting choice deserves its own moment, because it changes who does what after launch. With Apple-hosted assets, Apple's documentation says you upload your asset packs to App Store Connect and maintain them there, much like app builds, and they need to be uploaded before you distribute the app through TestFlight or the App Store. That keeps everything in one place your developer already uses, and it means content changes go through the same account and people as releases.
Hosting the content yourself gives you more control and more work. You run the servers, you pay for the bandwidth, and you own the job of keeping old and new versions of content available for people who haven't updated the app yet. For a small team with a catalogue that changes every week, that may be worth it. For a language course that changes twice a year, it probably isn't.
There's no universal right answer. The useful thing is to make the choice on purpose, early, and to write down who is allowed to change downloadable content once the app is live.
Questions for your developer this week
You don't need to read Apple's documentation yourself. You need three short answers from whoever builds your app.
Does our app use On-Demand Resources today, and for what? If yes, which screens depend on it, and is there a plan for 2027?
Is anything on our roadmap that downloads content after install, such as lessons, levels, catalogues, maps, offline manuals or seasonal content? If yes, is it being built on Background Assets?
Who would host that content, Apple or us, and who updates it? That decision affects cost, release process and who on your team can change content without a developer.
One last point from Apple's documentation: Background Assets is only for downloading additional assets for your app. It isn't for collecting data to identify people or devices, or for advertising measurement. If anyone proposes using it for something else, that's a no.
If you're planning an app with downloadable content, or need an older app moved off On-Demand Resources without disrupting users, that's the kind of work we do in mobile applications. Talk to us.
Related work: Sutton|Place
We build alongside the people doing the work.
Bring us the problem you’re thinking about.