20 comments

[ 4.1 ms ] story [ 53.5 ms ] thread
I guess next in the pipeline is TweetDeck Web Desktop App :)
Isn't this exactly what Twitter said they DON'T want to see (replacement clients using the Twitter API). Is TweetDeck just "grandfathered in"?
They "recommend" people don't build businesses like TweetDeck, because they believe there isn't enough room. However, it seems to me that TweetDeck has done pretty well for itself.
FTI - here's the Twitter developer group post:

http://groups.google.com/group/twitter-development-talk/brow...

It seems stronger than merely a "recommendation" to me. They flatly state that new apps may not replicate the mainstream Twitter experience. Existing developers are allowed to continue to "serve their customers" - but I think developing new product lines as TweetDeck is doing, is going to run afoul of the new API terms of service.

Unless they have a side agreement, I expect some sort of battle to arise from this.

I guess the same can be said for Seesmic Web.
I would assume TweetDeck is grandfathered in. However, it does make for interesting discussion when monitization roles around...

    Twitter: Want unlimited API calls?
    TweetDeck: YES!
    Twitter: Okay, thats $XX,XXX a year...
Tweetdeck is probably okay until twitter decides that their business is being hurt too much by them.

Though there is always the chance that twitter tries to buy tweetdeck.

Twitter have specifically said that they don't want new twitter clients. However the already existing ones are mostly fine.
Completely quixotic. Twitter wants to own the client experience and as owner of the platform, they have the power to do so.

Twitter's now-infamous developer group post also listed a number of areas Twitter doesn't want to own. Reading between the lines, they're giving client companies the opportunity to transition to another line of business. If the client companies don't take the hint, Twitter's going to eventually play hardball.

Why doesn't Twitter buy TweetDeck? TweetDeck appears to be a better user experience than anything that Twitter have come up with themselves so far. If Twitter does want to own the client experience on their platform then what better way of doing so?
We've been working on something like this but better for a while: http://meeep.com A totally customizable Twitter web client (e.g., you can upload your own userscripts, HTML templates, etc.).
This is based on the core of the Google Chrome app. Does this mean it is expected to replace the Chrome app? And does it have any new features? I've been missing the ability to filter certain apps from the Chrome app yet still find it the best Twitter desktop app.
How interesting! This could put Twitter in a very interesting place -- perhaps, one day, they won't need to maintain a client for their service!