/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

The End Of Blippy As We Know It

So it turns out that almost nobody wants people to check out their purchases.  And also that just adding a social element to a feature isn't enough to make it useful.  The lessons of user adoption are sometimes learned the hard way.

TechCrunch Alexia Tsotsis

Context & Ripple Effects

Blippy's pitch was that friends would want to see each other's purchases streaming from credit cards and retail accounts, and through 2010 it fought to keep its data pipes open — most visibly with an OAuth workaround through Gmail to restore Amazon support after the direct integration was cut off.

By May 2011 that fight is over: per TechCrunch's own post-mortem, almost nobody wanted their purchases checked out publicly, and bolting a social layer onto a transaction feed wasn't enough to make it useful. The failure is now the reference case for what happens when sharing financial data meets actual user apathy.

First-order effects

  • Blippy's users lose the purchase-sharing feed entirely, and any retailers or card-linked integrations built around the service lose their showcase for social commerce.
  • Amazon's earlier withdrawal of support, which forced the Gmail OAuth end run in April 2010, is vindicated — the demand side never materialized even with the data plumbing restored.

Second-order effects

  • Other startups pitching purchase-sharing or social commerce will find investors asking the Blippy question first: is anyone asking for this, or is the social element doing all the work?
  • Retailers and payment partners weighing 'share your purchases' integrations get a cautionary data point on opt-in rates, making them more likely to insist on utility beyond display before granting account access.

Third-order effects

  • If the pattern holds, financial-account access for consumer apps gets gated behind demonstrated retention rather than novelty, and 'social X' products are judged on whether the underlying behavior exists without the social layer.
  • Consumer social products built on sensitive personal data face a higher bar: one privacy stumble or one flat growth curve can be terminal, because the data-sharing consent that powers them is the first thing users revoke.

The trend: Social-commerce products that assume people want to broadcast transactions keep failing to convert novelty signups into habits, pushing the industry toward utility-first models where the social layer is optional.