blog.ChrisRicca.com

Maybe twitter isn’t that popular…

Twitter has not yet become as popular as the continuing extensive media coverage surrounding it would make you believe.  My evidence?  Take a look at this snapshot of a Google trends query for “facebook, twitter”:

The graph on the bottom represents how I used to feel twitter was doing with their mass-market adoption.  It portrays what we’ve all witnessed over the last year: all out love-fest on the part of the news media, who have embraced twitter and promoted it vigorously to viewers and readers (and with good reason: it’s a distribution service - content creators *should* love it).  The effect, however, has been a bit misleading.

When you look at the numbers of Google users who are searching for ‘facebook’ or ‘twitter’ (the top graph), the juxtaposition brings the hyped nature of Twitter into stark relief.  It’s not that Twitter’s growth hasn’t been healthy.  They have grown their product amazingly well, but the exposure we see in the news does not reflect a true wide adoption on the part of users.  I’m a big fan of the Twitter team and their API approach; this isn’t a comment on the past or future success of the service.  But, in an world that moves as quick as ours, it’s important to question our assumptions before they get the better of us.  I previously assumed that Twitter had achieved mass market adoption; Now, I’m not so sure they have.

A quick story about Art and the internet

Natasha Wescoat sent me an exciting email this past week to tell me she had finished a work I commissioned about a month ago.  I heard about Natasha through Hilary McHone, who retweeted Natasha announcing she had some time for commissions, if anyone was interested.  My wife and I have been meaning to adorn the walls of the apartment we’ve now been living in for three six seven months, so after a quick google image search to see what I was getting myself into, I replied that I would love to commission some art!  Why not?

Not sure of how to proceed, I sent Natasha a drop full of some photos I plucked from iPhoto for inspiration, and a number of her works that I especially liked.  (Someday she’ll tell me if this was an interesting way to work…to be honest I had some reservations about influencing the artist too much)

Natasha disappeared for a few weeks and then this past weekend, this photo appeared in my inbox:

Cool, huh?  I dig it when technology facilitates art and artists, and brings artists to an audience.  Straight from a retweet to my wall.  If I can just figure out which one to hang it on…

Twitter, Foursquare, and the Interface API Strategy

This post is prompted by Gowalla’s recent announcement of a read-only API.

Twitter users often describe the service as “Facebook status updates by itself, without the other stuff”.  This description is my favorite way to talk about the strategy behind Twitter’s design and their API, and what this strategy means for other startups charting a similar course.

Here’s my short version of the Interface API Strategy to World Domination:

Phase 1: Build a service around a single UI interaction (“What are you doing?”) and some basic but useful infrastructure (followers)

Phase 2: Leverage the simple API to spur the development of clients across all platforms and new value for users

Phase 3: Become the Internet Standard for your interaction and the resulting data

Phase 4: Profit.

It’s way more fun than collecting underpants.  By optimizing for a simple API focused on on user interaction, you get a hoard of hackers, hobbyists, and entrepreneurs who want to play in this arena fighting by your side, as well as the possibility that the progressive executive in that old media company will understand, without a 30 minute presentation, the kick-ass opportunities your service offers.  Twitter is already well on their way to becoming a standard interface on the web; I think they have small form distribution in the bag.

But now, we shall look into the (near) Future!  The next interface API victory story will be a location check-in service.  A once exciting web service cage match between newcomers Foursquare and Gowalla is proving to be something of a rout, with the scrappy and lean Foursquare announcing a new Old Media partnership every couple days or so, while Gowalla, laden down with a lot of new cash, fails to respond with a proper API.

Foursquare’s API, a huge driver of the service’s success, has all the characteristics of a winning design: their database structure is easy to understand, especially if you’ve used the service even once, and they allow full read/write access to almost every object.  Gowalla’s object structure is similarly straightforward, so they have the cash and the position to compete, but until they open up write access, we only have one location check-in interface API in the ring.

Check-ins: check.  What’s the next simple interface API?

http://www.chrisjordan.com/current_set2.php?id=7