Interview: Mike Langford of Tweetworks - Page 2
Tweetworks was designed from the ground up to facilitate great conversations. Let's look at the very simple concept of threading for example. If I only have 140 characters for my message why on Earth should I be forced to fill it with the same three, four or five usernames over and over again to have a conversation with my friends while I watch the Red Sox game or manage multiple conversations to ask for help finding a local WordPress developer?
Tweetworks keeps the conversation together in a fully threaded fashion so users can interact quickly and easily with full context. When a new reply is added to the thread all participants see it because they are in essence "subscribing" to the conversation.
The experience becomes even richer when we look at Tweetworks groups.
I think David Pakman, of Venrock, phrased it best at Twitter's Chirp conference when he said that he sees the need for the "right-time web" in addition to the real-time web.
Much of the innovation in the Twitter ecosystem has been about managing tweets and connections as fast possible to harvest real-time intelligence but as David rightly pointed out, "nothing out there is delivering information to me at the right time when I actually need it." And until the introduction of Tweetworks groups that was true.
But now, with groups, Tweetworks users can create a topic, give it a rich description, add tags and soon other meta-data. This system makes it easy for people to find and join relevant conversations on just about any topic imaginable.
The most important distinction between Tweetworks and the other clients however is the fact that it is not just an application. Tweetworks is a robust platform with an extremely powerful API.
Just about everything you see on the site is available through the Tweetworks API. Even tasks like photo sharing and OAuth authenticating for Twitter profiles are handled on the server side and made available through the API.
It is my hope that we will start to see developers, including some with existing Twitter clients, leverage Tweetworks for their own applications. I see the existing Twitter client ecosystem not as a crop of competitors but rather as a huge group of potential partners.
A full list of features is listed on Tweetworks.com.
TR: You recently launched an iPhone app? What lessons did you take from other popular apps that impacted the development of Tweetworks for the iPhone?
Langford: Yes, the iPhone app is very exciting. As you know there are a lot of Twitter applications for the iPhone and they all seem to bring something valuable to the market. I certainly looked at many of these applications, as well as other non-Twitter apps, for inspiration during the design process.Continued on the next page