Google Photos continues syncing photos when app has been deleted from device; stops only when settings in Google Play Services have been changed
Jerry Hildenbrand / Android Central :
Context & Ripple Effects
Weeks after Google spun Photos out of Google+ as a standalone Android app promising free backup for images up to 16MP (per Re/code's review), Android Central has found the fine print: the sync engine does not live in the app at all. It runs inside Google Play Services, the system-level layer every Android device ships with, so deleting the Photos icon changes nothing — uploads continue until a user digs into Play Services settings to switch them off.
First-order effects
- Users who believe deleting the app ends their cloud backup keep uploading photos indefinitely; the actual opt-out is buried in Google Play Services settings most owners never open.
- Google gets continued photo ingestion and engagement from people who have explicitly removed the product — growth the uninstall metric never captures.
Second-order effects
- The discovery forces Google into reactive control work: months later it shipped a feature letting users delete on-device copies of already-backed-up photos, an early acknowledgment that backup state needed visible user management.
Third-order effects
- If the pattern holds, Android's user-visible apps become shells around a persistent Google services layer — which is where the company eventually converged, replacing the Play Services backup machinery with unified Backup by Google One in 2021. A platform owner running background sync outside app boundaries is precisely the structure that draws regulator attention to consent and default-on data collection.
The trend: Android is consolidating Google's consumer services into a system-level layer that persists across app installs and deletions, trading user-visible control for seamless default-on backup.