I’ve been using TweetDeck, primarily on my iPhone, as my only Twitter client for a few years. Several months ago, we were informed that the iPhone version of TweetDeck would stop working. If memory serves, it was supposed to go belly up in March, and it was about that time that the Facebook integration stopped working. That didn’t bother me, so I continued using it until just last week when my custom feeds stopped working. For those of you that aren’t familiar with it, TweetDeck would allow you to set up multiple feeds, including the standard timeline, mentions, and direct messages, but also allowing you to create custom feeds based on hash tags, keywords, and handles. It was very robust. I had one feed that listed any tweets referencing DesignAday, one that tracked tweets about IxDA, and I would set up feeds for each conference I was attending. I could easily swipe between them, and it would indicate which tweets I hadn’t read.
I’ve now been using TweetBot for about a week. It is a well-designed app—no doubt about it. There are many little details that make it a pleasure to use. However, I don’t find it to be nearly as convenient. It allows me to save searches and access them, but search feeds are treated as second class citizens. I have to first navigate to the search screen and then select the search stream I want to see, rather than listing them at the same level as my timeline. I could live with that, but it doesn’t retain any history of past viewings. Every time I view a search stream, it displays the most recent tweet, leaving me to read through them in reverse-chronological order until I get to one I’ve seen before.
I also manage my church’s Twitter account, and TweetDeck allowed me to include that feed at the same level as all the others. I could just swipe over to it. In Tweetbot, I have to switch accounts to see it.
TweetDeck always seemed like the “Pro” Twitter client. No other client I’ve tried has provided close to the same level of utility and flexibility.