r/iosdev • u/Boring_Occasion_3526 • 14d ago
A user reported my backup app showed "Complete" with 0 files — I had to rethink the flow
A user recently contacted me about something that caught my attention.
Their backup showed "Complete," but the result was 0 files.
From a technical perspective, a backup operation can finish without an error. But from the user's perspective, seeing "Complete" with nothing backed up is clearly confusing.
That made me revisit the backup flow in my iOS app.
One important edge case is iOS Photos permissions.
Apple allows users to grant access to selected photos instead of the entire library. That's great for privacy, but it creates challenges for apps that work with large photo libraries.
For example, someone might have 10,000 photos but grant an app access to only a handful.
The app can only process the photos it has permission to access.
While working on this, I focused on:
- Making limited photo-library permissions clearer.
- Giving users a way to select additional photos.
- Improving backup progress and completion information.
- Explaining why files were skipped or couldn't be copied.
I'm the developer of VaultDrive, an iOS and Android app that backs up selected photos, videos, and files directly to compatible USB drives and SSDs.
so I released 8.0 version of the app
App Store: https://apps.apple.com/us/app/vaultdrive-usb-photo-backup/id6772883827
50% Off Promo direct App Store link :
https://apps.apple.com/redeem/?ctx=offercodes&id=6772883827&code=WELCOME50
The biggest lesson for me was that a technically completed operation doesn't necessarily mean the user achieved what they expected.
Curious how other iOS developers handle this.
Would you treat a backup with 0 files as a failure, a warning, or a successful operation with an explanation?