An rssCloud case study: Brizzly & Seesmic

07Sep09

A picture named ninja.gifThere’s a lot of sides to a bootstrap. The idea is to take a something that’s highly integrated and break it into pieces. Connect the pieces with open formats, and then show people how to compete. Then each of the pieces becomes a market where users have choice. And when users have choice, competitors must work hard to please them.
It’s how we got RSS going in the first place. Netscape got a few content companies to create feeds. They created an aggregator, which we competed with. Two aggregators, that meant more, for sure. And then we made our blogging software produce feeds and worked with lots of publishers. Now blogging software updates millions of feeds every day. But at one point there were just a half-dozen feeds and two aggregators.
There’s lots of competition in the market for Twitter clients. There’s a raging battle between a dozen teams all of whom are vying for your attention. Each of them wants to produce the product that attracts the most users. However at the center of the market there is no competition, so improvements come slowly. Our goal is to change that.
Now, two excellent examples of clients are Seesmic and Brizzly. There are many others but these are the two that I use, so I am most familiar with them. Here are screen shots of the two products. (Click on the thumbs to see larger versions.)
A picture named seesmicsmall.jpg
A picture named brizzlysmall.jpg
There are two ways they can support rssCloud, and help the bootstrap give more choice to users, and potentially free themselves to create more features without having to wait for Twitter.
1. Allow your users to subscribe to cloud-enabled feeds. Right now, most of those are the 1151 feeds of the people I subscribe to. But soon (knock wood) there will be many thousands more, content that you can’t get from Twitter. So supporting cloud-enabled feeds now could buy you a head-start on your competition in October or November.
2. Publish each user’s stream of 140-character messages as cloud-enabled feeds, in addition to pushing them through Twitter. Several reasons to do this. First, you provide them a backup, which may be a feature that’s of value to them. And they might be able to share their content with 140-character networks formed by others, including Facebook, Yahoo, Google, who knows who. Open formats and protocols create lots of options. Maybe you want to start your own little network of users independent of Twitter. I can tell you — I do! (And will.)
Brizzly and Seesmic may not want to do this now. After all it is a holiday weekend in the US. But you never know what the future holds, and it doesn’t take much time to think about it. “;->”



No Responses Yet to “An rssCloud case study: Brizzly & Seesmic”

  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: