FAILDEX失樂園
中文

Shadows

The business, the turning points, and the decisions behind them.

Event year2006

01 / WHAT IT BUILT

What the company did

Shadows was Pluck’s social-bookmarking product, supported by the Flock browser.

02 / Shadows FAILURE REASONS

Failure reasons

Pluck redirected attention to Blogburst and stopped adding Shadows features. Flock consequently removed support. The evidence establishes reduced investment and integration loss, not a verified date when all Shadows operations ended.

03 / EVENT HISTORY

Events in the structured record

  1. Browser integration withdrawn

    In November Flock announced Shadows would not be supported in its forthcoming release; Pluck’s CEO said Blogburst had its full attention.

04 / CONTEMPORARY REBUILD ASSESSMENT

Difficulty of rebuilding this project today

Material for this section is being gathered and checked. It will appear here once ready.

Rebuild difficultyPending assessmentNot completed
Scoring basisNot completed
ScalabilityPending assessmentNot completed
Scoring basisNot completed

Overall assessment: Not completed

05 / AFTERMATH

Lessons

Shadows' lesson is about being a side project inside someone else's company. It was Pluck Corporation's social bookmarking service, distributed through the Flock browser — but when Pluck decided its Blogburst publishing platform deserved '100% of our attention' and phased out consumer-facing products (including the Shadows bookmarks product and its RSS reader), the service died with barely a funeral notice. It lost to del.icio.us not because bookmarking was a bad idea, but because the team that owned it stopped caring. The lesson: if your product's survival depends on a parent company that doesn't need it, you don't have a company — you have a borrowed audience, and it can be taken back at any time.