Flud
Flud was a mobile social news reader that let users follow sources, save articles, and share reading activity across phones and tablets.
View original storyProduct snapshot
What it was
Flud let users follow news sources, save articles, and share reading activity across mobile devices.
Who it was for
Problem / value
Tried to make news consumption more social and personalized than a standard feed reader.
Core workflow
- read news feeds
- save articles for later
- follow users and share reading activity
- organize content after the enterprise pivot
Core dependency
Reliable onboarding, repeat reading behavior, differentiation in a crowded reader market, and a credible monetization path.
Product form
Pricing model
No stable public pricing model found; public sources emphasize funding, consumer usage, and an enterprise pivot.
What happened
Summary
Flud shut down in 2013 after failing to turn social news-reader attention into product-market fit and monetization.
Outcome
TechCrunch reported funding and product-market-fit struggles; Phandroid reported the service shutdown date.
Demand signal
Public sources show early buzz and funding interest, but the company still struggled to find product-market fit, monetization, and enough runway. Early press also exposed product reliability issues.
Distribution issue
Press and app-store attention brought users before the product loop was ready. In a crowded reader market, Flud also had to compete with stronger alternatives and unclear differentiation.
Timeline
- Launched around 2010
- Raised seed financing according to TechCrunch
- Explored consumer and enterprise directions
- Service shut down in August 2013
Before you build
Why it matters
Consumer app attention can look like demand, but it can also expose weak activation, bugs, and unclear repeat behavior.
Primary check
Treat launch attention as a stress test, not proof of demand: validate activation, retention, monetization, and reliability before seeking broad press or app-store traffic.
Checklist
- Run reliability and onboarding tests before press outreach.
- Measure retained readers by cohort, not total installs.
- Validate monetization with a small segment before pursuing broad coverage.
- Can new users complete the first useful reading session without bugs or confusion?
- Do week-four cohorts still read, save, or share content?
- Is there a credible paid customer or revenue model?
Relevant if
- You are building a consumer content app, social reader, or mobile app that depends on launch buzz.
- You are relying on press, app-store installs, or social sharing before retention is proven.
Less relevant if
- Your product has a proven paid workflow and is not dependent on broad consumer attention.
Pre-build tests
- Invite a small cohort and require repeated reading or sharing before public launch.
- Test pricing or enterprise demand before building a full pivot around it.
Transferable lessons
- Validate product reliability before broad launch.
- Treat press-driven installs as a stress test, not proof of product-market fit.
- Do not pivot to a new customer type until retention and monetization gaps are understood.
If you build this today
Launch to a small cohort first. Measure first-session success, week-four retention, saved/shared articles per user, and willingness to pay before adding social features or pursuing wider coverage.