Backup, Restore, Migrate
summary
Android device migration focuses on using Auto Backup plus an encrypted Cloud Key Vault so app data is encrypted on-device and Google cannot read backups; default auto backup saves shared preferences and internal storage (unless over 25 MB per app quota), excludes caches and supports an XML include/exclude list for granular control; key/value backup is deprecated, developers must opt out to exclude data or adjust what gets restored to avoid huge unwanted uploads.
AI-written summary · about
chapters (9)
- 0:00Introduction and problem
- 1:56Data privacy with Cloud Key Vault
- 3:42Android security model explained
- 5:50Developer control over backups
- 7:39Android Auto backup details
- 9:24Custom backup with XML files
- 10:48Future of backup and migration
- 12:12Key value backup limitations
- 13:14Q&A and next steps
related talks
12mBackup, Restore, Migrate
45mAndroid Backup, or How to Save the Business Millions
26mSafely Migrating to DataStore in Production
47mRemember Everyone: Autofill Framework and Account Transfer API
06mOptimizing user flows through login
26mWhats new with Data Storage?
47mAuthenticator Leakage Through Backup Channels on Android
23mUser Initiated Data Transfer Jobs