Five Things Twitter Should Do in ’09

What’s up for Twitter in 2009 after a pretty spectacular 2008? Here’s a list of my suggestions:

1. Launch a business model and/or business models. Sure, it’s been discussed incessantly for months and months but Twitter now has the critical mass and, hopefully, a good enough infrastructure to get the business jump-started. With advertising pretty much dismissed by Twitter as a business model, it looks like a move into the corporate market could be in the cards. That said, I think Twitter users would tolerate some advertising if it were relevant and useful.

2. Diversify the Twitter client. Twitter.com is, well, boring. It’s like vanilla or chocolate ice cream in a market where third-party developers are making out like Ben & Jerry with clients and online services featuring much more interesting bells and whistles. Maybe Twitter should buy Thwirl or Tweetdeck for people who like desktop clients. And for those who like online service, SplitTweet, Tweetree and EasyTweets could be good additions to the Twitter portfolio.

3. Create a WordPress-like developer ecosystem that would make it easy for developers and user to find the tools and related services/widgets to enhance the Twitter experience. Right now, finding new and interesting Twitter services can be painful because there’s no one place to get what you want.

4. Make the Twitter API more user-friendly for developers, especially the authentication process. This would make Twitter more secure for users and make it easier for developer to unveil new services. For more on Twitter’s authentication flaws, check out this post by Reality Me.

5. Launch or encourage the launch of TwitterCamps. Clearly, there’s huge interest in Twitter and expanding the ecosystem so support events to bring together users and developers would be a great for the community and the company.

Technorati Tags:

This entry was posted in Uncategorized. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.

10 Comments

  1. Posted January 2, 2009 at 3:18 am | Permalink

    All good ideas, though I think twitter's first priority has to be stability. Their business model could/should rely on third party APIs that can be brand integrated including and beyond OLA. The wordpress angle is interesting, certainly something to think about.

    From a funcionality perspective, would you want to see broader capabilities? Maybe broader cross-network capabilities?

  2. Posted January 2, 2009 at 3:29 am | Permalink

    I've set up a petition asking Twitter to provide remote keys for third party applications to prevent information harvesting. Here's the link: http://friendfeed.com/e/eedc6caf-5e5e-4557-8abb-1…

  3. Posted January 2, 2009 at 5:51 am | Permalink

    Mark maybe you should get things rolling here in T-dot by planning a Twittercamp.
    An unofficial mesh-exentsion, maybe?

    • markevans
      Posted January 2, 2009 at 8:08 pm | Permalink

      I just may do that. :)

  4. Posted January 2, 2009 at 6:00 am | Permalink

    I agree with needing to expand, but they've also been more successful than other similar clients by keeping things ultra-simple. Wonder what's best for Twitter's future.

  5. Posted January 2, 2009 at 6:44 am | Permalink

    I agree with Brandon – Twitters remarkable success is because it has been kept so simple. Personally I hope that the platform can achieve better stability……and not change beyond that.

  6. Posted January 2, 2009 at 6:45 am | Permalink

    While I am an advanced social networking site/app user, I like the simplicity of Twitter. Some sites get so bogged down with apps and enhancements that they are difficult for new users (especially adults) to grasp. I do like the idea in #3, though, where it could be optional to add widgets.

    Kind of torn here-I love extended capabilities for myself, but not more than stability, and I hate having to teach people how to use sites!

    Good post.

  7. Posted January 2, 2009 at 12:43 pm | Permalink

    Surprised not to see any enhancements on the list like groups or pics.

  8. Posted January 3, 2009 at 2:30 am | Permalink

    Nice post and you are on target with most. Regarding #2 I have to disagree. I think that the interface should stay super simple.

    Perhaps using keyword monitoring as a "pro" feature might help develop a business model. Let the developers earn a commission by using promoting a desktop client that upsells the pro features.

  9. Posted January 4, 2009 at 2:03 am | Permalink

    Keeping the twitter interface very clean is the number one reason that I use it. Bringing on more bells and whistles will more than likely make me shy away.

2 Trackbacks

  1. By links for 2009-01-06 | stuart henshall on January 6, 2009 at 3:05 am

    [...] Five Things Twitter Should Do in ‘09 | Twitterrati This would just be the beginning of my list. Number 4 is crucial for security. I'd just like to see a forum held with developers and it might help if they spent more time actually encouraging the ecosystem. (tags: twitter) [...]

  2. [...] Five Things Twitter Should Do in ‘09 | Twitterrati A great list to make sure your efforts are going somewhere (tags: twitter socialnetworking socialmedia socialnetworks goals marketing) Vertical1236142 = false; ShowAdHereBanner1236142 = true; RepeatAll1236142 = false; NoFollowAll1236142 = false; BannerStyles1236142 = new Array( “a{display:block;font-size:11px;color:#888;font-family:verdana,sans-serif;margin:0 4px 10px 0;text-align:center;text-decoration:none;overflow:hidden;}”, “img{border:0;clear:right;}”, “a.adhere{color:#666;font-weight:bold;font-size:12px;border:1px solid #ccc;background:#e7e7e7;text-align:center;}”, “a.adhere:hover{border:1px solid #999;background:#ddd;color:#333;}” ); document.write(unescape(“%3Cscript src=’”+document.location.protocol+”//s3.buysellads.com/1236142/1236142.js?v=”+Date.parse(new Date())+”‘ type=’text/javascript’%3E%3C/script%3E”)); Please Share and Enjoy: [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

  • Mark’s Blogs

  • Find ME Online

  • Twitter Updates