Branded Tweetdeck – Great Idea or Waste of Time?

Not In The Way... Not At AllWhile I don’t use third-party Twitter app Tweetdeck myself (I switched to Seesmic Desktop a while back), I noticed today that both Mashable and TechCrunch now have their own branded versions.

It’s basically the same Tweetdeck application but now you can have a dedicated pre-set column for the latest news from both websites, as well as a shiny Mashable or TechCrunch logo on your Tweetdeck skin.

But are they worth changing to?

Personally, I can’t see the major benefit at this time. Yes, it’s great that now both Mashable and TechCrunch have their logo on Tweetdeck’s interface. But will that really expand their brand?

I’m guessing that most users who already have Tweetdeck installed know about both websites. And you can always just set up your own preset column in the standard Tweetdeck to watch the Mashable and TechCrunch feeds.

What about new users? Mashable promotes their version by saying it’s great for new Twitter users to “get up to speed”. I’m not so sure – new Twitter users might be better getting used to Twitter itself first before trying to control a multi-column app.

Comments on both websites are mixed – some think it’s great while others think it’s a waste of time.

I have to say that I’m with the second camp at the minute. It’s always interesting to see brands experiment with ways to get their name into people’s collective. I’m just not sure this is it.

And with some Tweetdeck users still complaining about performance issues (the new iPhone app crashing, memory hog, etc), wouldn’t it be better for Tweetdeck to concentrate on that first?

What about you? What’s your take on Mashable and TechCrunch’s new Tweetdeck app?

Would it make you question their bias when discussing third-party Twitter apps? How can they make real use of it down the line? Will you be downloading one of them?

Creative Commons License photo credit: dprevite

There are 30 comments Share your thoughts

Share your thoughts

Your email address will not be published. Required fields are marked *