Android Large Backups API: A Deep Dive for Data-Rich Apps
Android’s standard Auto Backup feature allows applications to back up a maximum of 25MB of user data to cloud storage. However, for apps dealing with substantial amounts of data – such as user-generated media, large databases, or extensive datasets – the Android Large Backups API offers a more robust solution. This API enables developers to securely back up larger data volumes, up to 50GB per file, leveraging the user’s Google One storage quota.
Key Advantages of the Large Backups API
The Large Backups API provides several benefits for data-intensive applications:
- Seamless User Experience: Automatically back up user data to the cloud, maintaining a consistent user experience.
- Reliable Data Recovery: Enable users to restore app data to its previous state in case of device loss, damage, or reset.
- Effortless Data Transfer: Facilitate effortless transfer of user data to a new device.
- Scalability: Accommodate growing data requirements and expanding user bases.
- Abstracted Backup Logic: The API handles complexities like backup scheduling and frequency, allowing developers to implement granular control within their app if desired.
- Extended Session Support: Data transfer periods can be extended to safely back up large datasets, subject to system-defined inactivity timeouts.
Large Backups API vs. Automatic Backups: A Comparison
| Functional Area | Large Backups API | Automatic Backups |
|---|---|---|
| Total Backup Size Limit | None | 25MB |
| Size Limit Per File | Up to 50GB | 25MB |
| Storage Impact | Included in the user’s Google One quota | Included in the user’s Google One quota |
| Transfer Method | Cloud only | Cloud or device-to-device transfer |
| File Control | Schedule, priority, and order can be controlled in detail for each file. | Define the files to include in the backup. |
| Restore from Settings | An app can initiate an on-demand restore of all or part of its backup data at any point in the app’s lifecycle. | Allows only user-initiated backups after initial device setup. Availability depends on the device and app. |
Program Eligibility and Application Process
Access to the Large Backups API is granted only with approval. The program targets large app developers, evaluating applications based on their data backup practices to ensure data utility and efficient backup processes. To request access, developers must submit an application ticket.
Eligibility Criteria
To be considered for the Large Backups API, applications must meet the following criteria:
- Significant User Base: Typically, apps with large user bases (e.g., 100 million monthly active users (MAU)) or those demonstrating significant technical requirements for bulk data egress. Apps with rapidly growing user bases expected to exceed this threshold are also considered.
- Data Volume and Type: Average over 1 GB of real-time user backup data per app per user. This generally applies to apps handling large amounts of user-generated content, such as:
- Messaging apps with media (photos, videos, audio)
- Note-taking apps with user-created media or rich text
- Apps with large databases of user-generated content
- Essential Data: The data backed up must be essential to the app’s functionality and not easily reproducible (e.g., user-created text, media, or documents). Apps backing up application cache or assets are not eligible.
- Backup Frequency and Data Change Rate:
- Backups should occur no more frequently than once a day and no less frequently than once a month.
- Apps with frequently changing data (e.g., chat databases) must implement efficient update mechanisms, such as byte-level differences, to minimize bandwidth consumption and resource usage.
- Data Security and Privacy: Apps must adhere to strict data security and privacy standards, complying with all applicable regulations (e.g., GDPR and CCPA). Apps using complete-to-end encryption are eligible if they implement backup procedures meeting Google’s security standards.
Google reserves the right to implement rate limiting, traffic quotas, or convert the API to a fee-based model. Violation of the Terms of Service may result in suspension or cancellation of API access.
Keep reading