If Twitter is part of your information ecology you are going to run smack into an interesting problem during the design phase – you have no control over the technology people use to access Twitter. Your users might come at you through a web app on the desktop or they might be using SMS on a cell phone. Or they could be seeing your tweets through a sidebar on topical blog somewhere. Yes you still need to design your Twitter profile page on the off chance someone will visit it (HOT TIP: use this Photoshop template) but the fact is that the only control you have over look, feel and function is your choice of avatar. OR IS IT?
The Tweet is the UI
It dawned on me this week that a single tweet is a user interface. Within 140 characters there are a surprising number of elements that you can control and some of them have profound design consequences. For instance, the choice of a URL shortener can have an impact on your analytics. TinyURL, one of the first URL shorteners, shortens links and provides users with a preview. Other shorteners like ow.ly, goo.gl and bit.ly also help you track click-throughs. And of course Twitter has its own automatic link shortener which doesn’t give you any analytics goodness but it does give your users some assurance against spammy links.
And that’s just one element of a tweet. For this reason it makes sense to me to put a single tweet through the design framework process, break it down to its basic elements and develop a list of “tweet best practices” to follow. This is for my personal online ecology redesign but I think it is even more important for businesses to consider.
It’s Best to Test
If Twitter is part of your business strategy then some user testing and design guidelines are crucial. What avatar best represents your brand as a personal entity (tip: it might not be your logo)? What gets the best response, @mentions, direct messages, hashtags? How does time of day impact your visibility in the tweet stream? What choice of photo/media sharing service provides the best value and viral functionality? What kind of conversational tone will you adopt and how much context will you provide in conversational tweets? Are you going to use location services or not?
That’s a lot of stuff to consider for a design element that is probably most often overlooked and almost certainly never considered in the design framework process. But think of it this way, a lot of the research that you do can be reused for other projects. And when you’re done with the design process for a single tweet you’ll be 140 characters closer to wrapping up your entire project.
{ 0 comments }




