OpenSocial, a group effort to create a widget platform spear headed by Google, has a few glitches that I’d love to see fixed. They are largely comparison items from Facebook, who has recently announced that it will open source it’s own platform. Regardless of the motivation, there are a couple of items I’d like to see ported from Facebook to OpenSocial.

1. Support for FBML like syntax: “Hold on a second! Standard HTML is the benefit of OpenSocial over Facebook” folks are probably thinking. While that’s true, without an effective way to capture and store user information for more than 24 hours (pesky terms of service documentation) developers are left querying for friends pictures etc over and over and over again. While this isn’t inherently a problem, if you wanted to display a 1,000 profile pictures for some unknown reason, you need to call the API a large number of times. Then generate the HTML and pass it to the client. This makes applications painfully slow. It’s great to store the numeric id (12345678) and be able to pass it back to the pre-client for parsing. The best examples are and . These really are very handy.
2. Support for FQL like syntax: OpenSocial does a great job of providing methods for gathering most of the information you would want from the social graph, but it’s lacking in the ability to remix the data in new and interesting ways (easily). OpenSocial requires all of the heavy lifting to be done on the client (or the application backend if their API allows it). Most clients have a reasonable limit as to how big data structures can effectively be and have the application still function. Processing on the applications infrastructure negates another advantage of OpenSocial which is requiring very little in the way of hardware to operate.

There are also some learnings here for Facebook. I’d like to see a few OpenSocial conventions ported from OpenSocial to Facebook.

1. OAuth Signature: To be fair, Facebook does provide signed requests, but it would be great if they’d use a standards based signature instead of their own homegrown version.
2. External JavaScript Libraries: Facebook’s FBJS is powerful and provides most functionality that developers need. It’s even been open sourced so it can be used outside of the Facebook universe. However, developers who’ve been working with jQuery, ProtoType or any of the other numerous javascript libraries have to start at the beginning again. Additionally, they may be missing the functionality in the FBJS library that they need.

Both platforms still have a ways to go in terms of making developers life’s easier and users application experiences more robust. I think it’s great news that Facebook is opening their platform more. It’s really more symbolic than anything, because they still ultimately control what they do or do not implement on their platform. Bebo is the only other social network using Facebook’s model and it still requires some re-writing for developers because of syntax difference and lack of some features.

Data portability has been a hot topic as of late. What I think everyone has neglected to consider is who owns which bits of data. For example, my email address is mine. I choose to give it out to friends, family, associates that I want to be able to contact me. That doesn’t, however, mean that it’s also theirs to use how they see fit.

For example, if you’re my friend and you wish to download your social graph to port it to Hi5, Ning or somewhere else, you should be able to do that. However, that doesn’t mean you can take my email, phone, physical address etc with you. What needs to be preserved is our association, not my data. This could be achieved by a public identity such as OpenId and a UUID value tied to each user – ideally the solution would be easier to create so even my mother could do it. Conversely, your data should be able to be ported to the new network without interference from Facebook, MySpace or anyone else.

What makes this discussion difficult is shared property. Consider a tagged photo on Facebook for a minute. I’ve taken the photo which includes you. To make it more complicated, let’s say you tag yourself in the photo. I still own the photograph, it’s even protected under US Copyright law should I choose to exert my rights. But you’re in it – and you want to use it as a profile picture… what to do? This type of shared relationship requires permission in my opinion. Since we’re friends, you know if I’m likely to grant you permission or not when you ask. This process could easily be automated. This could even be automated to the less vague bits of information such as contact information (email, phone, address etc).

Today marks a milestone for my Twitter usage. I tweeted my 1,000th tweet. What does that mean exactly, well, honestly not very much. However, as I scanned over the last 2-3 hours of tweets when I woke up this morning I noticed the increasing number of flame wars between thought leaders in technology frustrating. A feed of 20-30 tweets might contain 5-6 messages back and forth between folks who are in some sort of pissing contest about who’s right, wrong, cool or whatever.

It’s kind of sad.

As everyone struggles to really figure out how to effectively use Twitter it becomes hard to determine the best method for leveraging the technology effectively. I’ve been using it to keep up on industry insiders thoughts (which is probably why I get so much noise and childish banter in my feed). Others use it as initially intended, to tell folks what they’re doing and yet more for shameless self promotion.

I’d love to see more quality information from the industry visionaries who could all take a lesson from @jowyang and @guykawasaki and less banter about who’s right and who’s wrong. Guy and Jeremiah, and I’m sure many others, somehow keep above the fray and still add value to my Twitter experience.

Last Friday afternoon I wrote a MySpace application called Visitor Track. This is not a wholly original idea – nor was I the first to try it on MySpace. As of this writing there is even another application still listed in the application directory.

Before I explain how I went about going from 0 to 12,000+ users in a matter of 48 hours, I want to mention a few things.

1. It’s critical to understand that the MySpace audience clearly demonstrated a desire for more information about who’s looking (or not looking) at them.
2. Having a fantastic marketing plan will not make an application succeed no matter how cool YOU think it is, it needs to find an audience.
3. There is AMAZING growth potential in the MySpace application domain, even without notifications, invites and the viral components developers desire and users loath.

What I did was leverage the users profile well, provided a clean canvas with only what the user was expecting and was straightforward and honest in the application description. While I certainly could have leveraged advertising to promote the application, I chose not to so I could watch the growth of the application as it progressed organically.

The following chart is from Zynganomics who’ve been tracking MySpace applications since the initial launch of the platform.

As you can see, prior to the suspension of the application, growth was extremely strong.

Leverage the profile:

This is the single most important thing developers on the platform can do right now. With a general lack of viral push channels, developers need to hope that users find them. MySpace has recently started adding friend feed notifications about application installs and that has helped fuel growth through awareness within social circles.

The Profile for Visitor Track was a plain white box with two lines of text. I made the box as small as I could so it didn’t clutter the users profile with useless information. You can see what it looked like here:

The language, placement, size, color – everything – about the profile should be considered over and over and over and over again.

Name of the application:

The name of the application is very important. The largest viral channel available to applications today is the Friend Subscriptions. Basically a copy of the Facebook Newsfeed feature, this is the one place that the application will be seen by users you won’t otherwise touch.

Graphic design is over-rated:

My application about page had a poorly created icon and just a few lines of text to describe the application. I spent no time creating a fancy graphic interface – no time altering the colors of the page or install buttons with CSS and kept everything about as plain as it could be.

Compare that to the highly designed canvas pages of larger applications from widget giants like Slide and Rock You below:

Note: that the arrows facing the install buttons are animated in both cases and that neither app has more installs than Visit Tracker did.

Speed is everything:

If you aren’t tied to OAuth authentication and tight OpenSocial integration use an IFRAME – it’s less secure for you as a developer, but you ultimately control the communication between your application and your users. You’ll rely on REST requests to gather information about your users which means you’ll leverage the backend hardware more. However, what you lose in signed ajax requests and opensocial.postTo(), you make up for in speed and reliability. I’ve observed continual performance bottlenecks accessing AJAX content during peak times. While it’s reasonable to assume that this will continue to become more stable, now is the time to begin capturing audience before it’s too late.

Deliver:

Because it’s so easy to get started as an app and because the market of available users is so large, even knockoff applications can be quiet successful in terms of capturing users and market share. Consider the number of applications attempting to build on the success that applications experienced on Facebook like Honesty Box (of which I am a developer) on MySpace today (there are no less than 5 copycat applications).

It’s critical to deliver on what you told the users you would do! Below is a screenshot of the canvas (I omitted the right hand column which was advertising – a naive attempt to make money in this endeavor).

As you can see I kept it really simple. I leveraged the amazing Google Charts API for the graphs and the rest is just text. There’s gold in them hills, and a diligent miner with the appropriate tools will find it. Even this relatively little application had nearly 20K page views, which monetized effectively could yield ~$120/month or more.

I want to apologize to any MySpace users and employees who might have been offended by my application. I sincerely hope you’ll forgive my transgression against the TOS and that we can make beautiful applications together in the future (that don’t violate the TOS).

I’ve been experimenting with Twitter for just over 4 months now, using it in my personal and professional life. There seems to be a large and still growing developer community building up around it churning out great applications, including one I heard about (via @purplecar on twitter of course). The application by tweetclouds.com aims to create a tag cloud (much like the one on this and many other blogs) from your tweets; you can see mine here in all it’s glory.

If you’re on twitter, follow me – I’d love to hear from folks who are experimenting with new ways of extending twitter.

Some other interesting tools include Twitter Stats, which received some coverage on TechCrunch in January.

Quite possibly my favorite is TwitterVision, a nice mashup leveraging the public tweet stream and google maps to visualize the public feed. Incidentally David Troy (the author) has also created FlickrVision, basically the same app but using photos instead.

There’s also Twitterholic a top 100 twitter user board, Twubble a great way to find people you might be interested in following (recently featured on FaceReviews), Twitterverse another cloud app but for the entire twitter universe and if your totally lost as to why anyone uses twitter, I recommend the Twitter in Plain English video by CommonCraft.

If I’m missing a way cool web based app, please let me know in the comments below. I’ll save desktop applications for another post, there certainly are plenty of those too!

The Cisco Applying Web 2.0 to Your Business Challenges video is a must watch for every company not fully immersed in the world of social networking and new media. Robert Scoble and Jeremiah Owyang. I can’t recommend this video about how using wiki’s, blogs, social media and interaction is changing (and has been changing) business for a long time. Basically, if your company doesn’t have someone immersed in social networking tools first hand – hire one. Get someone in your company to give you feedback on what’s going on in this space. You only need to see the first 30 minutes.

Hi5 (yet another social network) is launching their OpenSocial based platform today (well really tomorrow and over the next few weeks) and have done a really great job communicating with developers how stuff is going to work. For example, letting developers know what will and won’t be working in their release plan. Facebook and MySpace could learn a good lesson here in communication. Stop being vague with your plans and let your developers and advocates know what’s up. Facebook has made some great strides with their notifications around larger platform changes, but the small stuff is still an open question.

Today I noticed a new tab in the application editor making it infinitely easier for developers of OpenSocial applications to adopt the MySpace platform. I first said they should be doing this two weeks ago and I’m happy to announce that they are. They now allow for the simple monolithic XML file to define your application. This is a great step forward. Their platform is becoming more robust and stable each day. Kudos to them, but they still have a lot to do as Nick O’Neill pointed out yesterday.

I saw on Forbes this morning that Time Warner is buying the social network Bebo for $850 million. My experience with Bebo hasn’t been great so far, it’s a blend of the best parts of MySpace and Facebook, but without the reliability or audience size of either. Granted my experience has been narrow – focused primarily on application development after they launched their platform based on the Facebook’s FBML.

AOL, the Internet division of Time Warner, said on Thursday that it was buying the social networking site Bebo for $850 million in cash, placing it in position to go head to head with News Corp.’s MySpace as well as Facebook.

What AOL fails to realize is that it’s original online presence was in fact a social network that they channeled into a portal. Now they’re looking to buy the 3rd – albeit a distant 3rd – largest social network to regain their original community of users. Kind of sad actually. Stats on the top 3 networks from complete.com below. Notice bebo’s not much more than a blip on the radar of MySpace and Facebook. As they say, “good luck with that.” I hope they don’t spam all the Bebo users with free AOL CD’s.

Today MySpace announced that the shift to OpenSocial 0.7 is completed and now they’re actively debugging it. The problem is, that most of the critical components, such as the ability to make AJAX requests, for any company looking to more widely leverage their existing databases are unable to do any testing at all! After setting aside my fears that OAuth wouldn’t be implemented in time, MySpace delivered yesterday OAuth signed requests. I’m really thankful that we can now use OpenSocial 0.7 within their container, but I’d be much happier if it all was working more than 48 hours before the soft launch. Their relay proxy machines have been down for nearly 12 hours now, putting a great crimp in development time. Does Rupert Murdoch own a pizza delivery chain or a significant interest in Red Bull?