TweetDeck have really dropped the ball by removing group functionality. I can see it driving away power users in the long term.
Here’s my situation. I currently follow approx. 400 people (and have about the same number of followers in return). I have a pretty broad range of interests, so I currently have 10 lists set up and, ideally, would like to set up 5 more but can’t afford the resultant API drain. (As an aside, before TweetDeck went list-only I only had 2 lists. But now I’m pretty much forced to use lists in order to replicate the group functionality I previously enjoyed.)
With the old group setup I could set my “all friends” and “mentions” sliders pretty high (to give me updates every 90s and 5 mins respectively) and it would still only consume about 60% of my hourly API calls. I’d even occasionally crank the “all friends” up to a 60s turnaround.
With my groups now replaced by lists, the fasted turnaround I can possibly get by cranking the “lists” slider all the way up to 100% is about 4m 30s. Leaving some room for searches, “mentions” and “all friends”, it’s closer to 7m 30s.
7 minutes may still seem fairly zippy (and for a casual user who follows less than 50 people it still is), but having developed a Twitter usage pattern around the 90s turnaround for “all friends” (and thus, by extension, all my groups) it’s like night and day. For 90% of the people I follow, a 7m turnaround is fine, but the remaining 10% I follow (which includes many of my favorite Tweeters) often indulge in a rapid, quickfire pace of conversational tweeting for short term memes. Ie, someone could mention the movie Avatar and within the space of ten minutes there’s half-a-dozen of us who are suddenly engaged in a brisk exchange of tweets on the subject. With the new list model this isn’t possible; I’m now forced to completely revise the way I use Twitter.
I’ve currently settled on a compromise where I now have “all friends” updates coming in every 3m 30s, “mentions” every 10m and “lists” every 6m 30s. It’s not ideal but it’s as fast as I can get it and ensure I have enough API calls left over for searches (I have about six columns set up to search the Twittersphere for info relating to my blogs).
Because I can no longer get a fast turnaround of updates via my lists, I’m now forced to concentrate on my single “all friends” column. This isn’t ideal because I’m forced to wade through irrelevant material to get to the material that interests me at that moment in time. I’ve also noticed that the “mentions” aren’t updated very reliably. I’m seeing mentions via the Twitter web site GUI that never make it into TweetDeck. Similarly, mentions that did previously make it into TweetDeck randomly disappear and reappear. Sometimes I see just the old ones and not the new ones.
At this point I should mention that I actually have two Twitter accounts. Both of them are related to two different blog projects with two very different sets of followers (one’s a retro video game blog, the other’s a book review & writing critique blog). Thankfully each account carries its own set of API calls, so the number of lists I have in one doesn’t impede the other.
At some point in the future, I can see myself having to create another account or two. On one set of accounts I’ll just follow the news/information providers, while on the other set I’ll follow the conversationalists. If TweetDeck brought back groups I wouldn’t need to do that, but if they continue with their list-only model I’ll have no choice but to create additional accounts.
Ideally, I’d like to see TweetDeck bring groups back but give us the ability to either sync them with an existing list or just create a proprietary group not connected with any list. These would then just effectively function as a filter for our “all friends” (as it did in the past) and not rape the API as much as a pure list would. The mind boggles as to why this wasn’t implemented in the first place. It looks like TweetDeck got a bit too excited about the potential for integrating lists and rushed to the list-only model without considering the consequences.
If TweetDeck ignore our pleas to bring groups back and steadfastly remain a list-only app, I can see their base of power users eventually drift away to other applications. I would use Seesmic but its interface is diabolical and setting up proprietary groups rapes the API (the last time I used it I worked out that it cost you 3 API calls to add a single user to a group. I added 50 users to a group in the space of 2 minutes and used up all my hourly API allowance. With 400 users to add to groups I decided I didn’t want to spend 8 hours doing 15 minutes worth of work and uninstalled it).
Please, TweetDeck, reconsider your approach to lists and proprietary groups. They can co-exist and aren’t mutually incompatible.