Martin Källström
knowledge / projects

Twingly Channels

Twingly Channels was a real-time, topic-based collaborative monitoring platform that inverted the social media model of the 2000s. Rather than following people, users could follow topics or themes, creating channels where teams and communities could collaboratively curate and discuss the most relevant content from blogs, microblogs, and social platforms. Developed and launched in 2009–2010, Channels represented Twingly's attempt to solve information overload while pioneering a distinctly social, real-time web experience.

The Problem: Information Overload

Information overload was the core problem Channels aimed to solve. ▶ 0:23 Twingly recognized that the fragmented social media landscape created an overwhelming stream of content, and ▶ 0:23 the company sought to extract a meaningful subset of that flow for end users. The goal was to Anders Thoresson ↗ help users find the two or three most relevant links each day instead of drowning in an endless stream.

Topic-Based Following: Inverting Social Media

The central innovation was a deliberate inversion of the social media model. ▶ 2:21 On Twitter and Facebook, users followed people; with Twingly Channels, users followed topics instead. ▶ 0:15 Anyone could set up a channel on a topic they cared about and invite others to collaborate on monitoring it—a model designed to ▶ 0:38 create spontaneous meetings between people with shared interests.

This framing allowed organizations to involve multiple departments in environmental scanning. ▶ 0:49 Not just information and PR teams, but sales and other business units could participate in monitoring the world (omvärldsbevakar) around them.

Architecture and Features

Real-time technology was central to the user experience. Channels used Anders Thoresson ↗ long polling to create a highly interactive, real-time feel for collaborative discussion and comments within each channel.

The data pipeline aggregated content from multiple sources: Anders Thoresson ↗ Twingly's own global blog and microblog search engines plus external social platforms including Digg, Delicious, Flickr, Wordpress.com, and Blogspot.

Channel structure combined RSS reader and social curation functions. Anders Thoresson ↗ Users created topic-specific channels and populated them with RSS feeds and search terms for continuous real-time monitoring. The approach differed from pure RSS readers like Feedly and Feedafever by Anders Thoresson ↗ emphasizing the social aspect explicitly.

Ranking combined user curation with Twingly's search index. Anders Thoresson ↗ Users could click to mark content as interesting, and ranking was also influenced by how many blogs and microblogs linked to a page—tapping both individual taste and crowd signal.

Business Model and Expansion

Twingly planned a two-tier business model. Free channels would be available to anyone from launch, with ▶ 5:22 planned public opening in 2010 where anyone could create channels without cost. For companies and organizations, Anders Thoresson ↗ premium offerings would include private channels for brand monitoring and internal team discussions.

Platform expansion was also planned. ▶ 3:03 Twingly intended to develop an API allowing third-party developers to integrate Channels wherever they wanted, and to build ▶ 3:03 iPhone and desktop applications for the service.

Martin was confident enough in the product to highlight ▶ 7:17 Twingly Channels as one of his own most-used websites for work, alongside Hacker News, his mailbox, and TechCrunch.

Roadmap and Timing

The concept had been Anders Thoresson ↗ in development at the concept level for approximately 1.5 years by August 2009. Anders Thoresson ↗ Martin felt the timing was right because technical solutions for real-time interactive experiences had only recently become available in May 2009, coinciding with Twitter's rapid rise in popularity.

Adoption Challenges

Martin was explicit about the central risk: Anders Thoresson ↗ users might perceive Channels as a single-player application rather than a social, collaborative tool—undermining its core value proposition.

The technical challenges were also substantial. Anders Thoresson ↗ Scaling real-time updates to many concurrent users in the same channel was a concern, but the larger challenge was behavioral: ensuring that users adopted the collaborative model.

Adoption strategy addressed this directly. Anders Thoresson ↗ In the initial phase, users would need approval to create new channels; the idea was to guide first-time users toward exploring and joining existing channels rather than defaulting to creating their own isolated ones. This design choice reflected a deliberate bet that seeded adoption and network effects would trump the openness of free channel creation.

Worth Remembering