Apple is working on a new framework that will allow third-party photo apps to back up images more reliably. Here are the details.
A long-standing request by photo app developers is about to be granted
Alongside the (likely) final stages of development ahead of the official iOS 26.1 release, Apple has also been working on a few new frameworks that should make their way to developers sooner rather than later.
One of them, as we covered here, will let developers join Apple’s new migration feature to and from Android.
Another, as Apple detailed in a new article on its documentation blog, will let developers enable background photo backups through PhotoKit.
Top comment by John Atkinson
I love to see more options available and made easier, what would be nice is greater integration in the photos app so the cloud app’s photos could automatically populate the default photos app that way it’s not just backups but can be an actual alternative to iCloud without giving up the default photos app but I doubt that’ll come any time soon although with some of the changes there making with interconnectivity who knows.
I’m mainly just hoping for a Time Machine like system for device backups where I can give an ip to point to(like a NAS) and just have it automatically backup.
Here’s how Apple describes the new feature:
In iOS 26.1 and later, PhotoKit provides a new Background Resource Upload extension type that enables photo apps to provide seamless cloud backup experiences. The system manages uploads on your app’s behalf, and processes them in the background even when people switch to other apps or lock their devices. The system calls your extension when it’s time to process uploads, and it automatically handles network connectivity, power management, and timing to provide reliable processing.
This means that third-party photo apps and even cloud backup services will finally be able to back up images automatically and reliably in the background, rather than relying on workarounds or waiting for the user to reopen the app.
In the highly detailed documentation article, Apple breaks down what developers will need to do in order to tap into the new feature, with steps including:
- Create and configure the extension target
- Enable the extension
- Process upload jobs
- Retry failed jobs
- Acknowledge completed jobs
- Create upload jobs
- Handle extension termination
Some of aspects of the new feature will require express user consent, while others will run automatically once the extension is enabled. Apple also notes that multiple aspects of the framework are still in beta, which means they are subject to change before the final release to developers.
Accessory deals on Amazon
- Apple AirTag 4 Pack
- Beats USB-C to USB-C Woven Short Cable
- Logitech MX Master 4
- AirPods Pro 3
- Wireless CarPlay adapter
- iPhone Air Ultraslim Magsafe Power Bank
FTC: We use income earning auto affiliate links. More.
Comments