A Bird in the Hand…

The recent release of Twitterrific 2 for the iPhone has reminded me that software development is replete with truisms. The primary thing I have to constantly remind myself is that, no matter what you do, or how hard you work, you simply cannot please everyone. Anyone who works in a creative field knows that there will always be those who are unsatisfied with the result.

For iPhone developers, these people usually fall into the “if it just had feature X, I would use it” category, but every so often you get someone who just poo-poos your efforts. It’s easy for devs to fall into the trap of trying to keep everyone happy, but years of experience have taught me that this is a losing battle. Development quickly builds into a sort of “features arms race” that usually ends with bloated software and burnt out programmers. No, the answer is to design first and foremost for yourself. If you can produce a piece of software that you are happy with, then chances are the majority of your users will be too. The trick is trust your gut enough to tell the difference between constructive feedback and the nay-sayers so you can move beyond them when it’s appropriate.

The other truism I’ve found is that there’s always room for improvement. The new posting user interface for Twitterrific 2 demonstrates this point perfectly. All through beta testing, the posting UI was the same as it was in version 1. If you wanted to change your update from one type of tweet to another, you had to toggle the tweet type using a single icon on the post bar. Although this method had served well since our initial launch, neither us nor the beta users were satisfied. Their feedback, combined with Louie’s desire to improve the posting experience challenged us to do it better. The result was a re-designed UI that fulfilled user’s desires for posting clarity while giving the Iconfactory a big new feature to tout. The amount of work required to pull off the revised posting interface so close to the end of the beta was intense, but ultimately worth it.

Lastly, if there is one axiom that Twitter has proven beyond a shadow of a doubt it’s simply that if you give an inch, the Twitterverse takes a mile. Lately I’ve been seeing more than a few requests for Twitterrific to support Twitlonger, a service that allows you to “expand” on the 140 character limit that is at the very heart of Twitter. The argument goes that allowing long updates to be read directly in-app is preferable to having to post multiple tweets. This may indeed be true, but I hesitate to support any service that, for lack of a better term, subverts Twitter. Brevity is the soul of wit, and in Twitter’s case, its lifeblood.

In my opinion, any update that can’t be held within Twitter’s 140 character limit should be taken offline to email, Facebook or Friendfeed. What’s the harm in supporting a great service like Twitlonger you ask? Seemingly none, except that Twitlonger is a very slippery slope. Imagine typing a tweet of any length right in Twitterrific. When the message length exceeds 140 characters, the app automatically creates web page entry where your followers can read your magnum opus. Sounds great, except its no longer Twitter, it’s called a blog. Given how easily such a feature would be abused (as is evidenced by the Twitterverse’s aggressive adoption of RT), I don’t see Twitlonger support in Ollie’s future.

As developers, all we can do is our best. Sometimes our best is good enough and sometimes it doesn’t cut the mustard. I’ve been very pleased with the positive reaction that Twitterrific 2 has been receiving from the Twitter community. There are updates coming that address some of the most requested issues from the initial 2.0 launch, but I have no illusions that even these updates will satisfy everyone. Not to mention all those people out there who are patiently waiting for an update to the Mac version of Twitterrific. To them, I offer one last proverb – Good things come to those who wait.