Blog Post

Tweetie 2.1 Update Brings List Support, New Retweet Implementation

Stay on Top of Enterprise Technology Trends

Get updates impacting your industry from our GigaOm Research Community
Join the Community!

Not one to be outdone by Twittelator Pro’s most recent update, atebits’ latest update for Tweetie 2 (iTunes link) brings implementations of the two newest official Twitter features: Lists and Retweet. As someone who isn’t particularly crazy about the official retweet implementation, I’m not so excited about that, but there’s still a “Quote Tweet” option as well, which lets you do things the old way.

There’s a lot of other new features and improvements, too, including tweet geotagging, spam reporting via the official Twitter API, What the Trend explanation of trending topics, and more. Once again, Tweetie has returned to the top of the heap, in terms of both functionality and UI.

Lists can be created, edited, managed and viewed, all from within Tweetie 2 now. That means if users post links in the “@user/list” format, you’ll be able to just click on it to view said list. Your own list management and creation features are accessible via the ellipsis (…) icon. I still have yet to create any of my own lists, but testing this out with the lists of others, it seemed to be well-implemented.

New video upload and hosting options are also available. You can now select from Posterous, Mobypicture and, in addition to TwitVid and yFrog. Maybe best of all among the UI changes, you can now disable automatic browser rotation, which is a feature every landscape-capable app should have, speaking as someone who often browses lying down in bed or on the couch.

Lots of other smaller changes and a long list of bug fixes are also included as part of the 2.1 update. The update is free for all Tweetie 2 users, but if you haven’t yet made the leap to the newest version, the $2.99 price tag is seeming incredibly reasonable right about now.

8 Responses to “Tweetie 2.1 Update Brings List Support, New Retweet Implementation”

  1. On the subject of the actual Tweetie update, this is absolutely wonderful.

    The new RT feature is implemented perfectly and hopefully this will cut down on all the RT spam people seem to be complaining about.

  2. @rubyvroom and @jeffrola – Clearly you either don’t understand Twitter or you happen to be following people that opt to Tweet too many mundane details. Twitter is an excellent announcement and promotion platform.

    I find that keeping up with products, services, and friends is so much easier on Twitter than it is with Facebook.

    There’s no clutter, no stupid Facebook apps to wade through to get to the content. It’s just a list of status updates, which is great. For me, anyway.

    Also, I’ve found that it’s much easier as a social tool than Facebook is, given it’s format and how many of my friends are using it. For example: I can make a tweet like “anyone want to grab dinner?”. I’m instantly hit back with restaurant suggestions, new places opening up to go check out, and of course, messages of whether or not people can come.

    It’s just a quicker and cleaner way to have some sort of collective discussion.

    Sorry you haven’t figured out Twitter, yet. It’s okay. My grandma hasn’t, either.

    • jeffrola

      I think Facebook is stupid, too. I keep in touch with my friends in REAL life…novel concept, I know.

      Facebook and Twitter only feeds the hubris of us ignorant Americans. We think we’re so damned important that people want to know about every little thing in our lives. Get over yourself.

  3. i partially agree with jeffrola, as it is now, twitter is not viable for mass adoption. that said, concepts and aspects of twitter have “shown the way forward” for communications within social networks such as 4[] (read foursquare) and iPhone app notifications, even if they are not 100% there yet. twitter to the world = not so much. easy, short communications within groups of genuine friends = awesome.

  4. I really don’t like the new (via @whoever) re-tweet implementation. I much preferred the old “RT @whoever” syntax. They should have made this configurable.

    I’m sticking with the old version until it’s fixed.