Google to shut down consumer version of Google+ in Apr. 2019 instead of Aug. and retire Google+ APIs within 90 days, after finding API bug impacting ~52.M users
After discovering another security issue potentially impacting 52.5 million users, Google today announced that the consumer version …
Context & Ripple Effects
Google+ has been in managed retreat for years: Google+ Photos was discontinued in 2015 once standalone Photos launched, and the Hangouts API was cut off in early 2017, leaving existing apps dead by April. This announcement accelerates the endgame — a second API bug potentially touching 52.5 million users' data moves the consumer shutdown up from August to April 2019 and puts every remaining Google+ API on a 90-day death clock.
The move matters because it converts a slow product wind-down into an emergency security response, and because Google later confirmed the April 2 date with full deletion of consumer content ([[a:938072]]), before eventually retiring even the enterprise successor, Currents ([[a:975945]]).
First-order effects
- Developers still integrating Google+ APIs have roughly 90 days to rip them out or watch their apps break, repeating the Hangouts API cutoff pattern at much shorter notice than the original August timeline implied.
- Consumer Google+ users face an earlier deadline: accounts, pages, photos, and videos get deleted in April rather than August, compressing any export window.
Second-order effects
- Enterprises that adopted Currents as the paid, private Google+ replacement inherit a platform whose consumer sibling died of API security failures — a trust overhang that foreshadows its own eventual wind-down.
- Third-party apps that survived the Hangouts API termination but still leaned on Google+ social features must absorb two breaking changes in quick succession, pushing them toward other identity and sharing providers.
Third-order effects
- The episode hardens a structural lesson for the developer ecosystem: Google's APIs carry retirement risk tied to both product strategy and security disclosures, so building on them demands exit plans — a pattern visible from Hangouts through Google+ itself.
- Repeated API-bug disclosures around user data strengthen the case for regulators and large customers to treat third-party developer access as a first-class permission boundary, not an afterthought bolted onto a social graph.
The trend: Google is consolidating its social graph ambitions down to zero — consumer, then enterprise — while its recurring API security failures accelerate the retirement cadence across its developer surface.