OpenSocial is OpenGadgets (and the de-portalization of content)
January 31st, 2008
I still haven’t got a clue what OpenSocial is really capable of…
Just read this by Steve O’hear who argues that OpenSocial should be renamed OpenGadget since “it’s all about standardizing the development of ‘widgets’ (sometimes called gadgets)”.
If this is so then I’m beginning to understand it and more importantly I’m actually beginning to find it rather interesting since most of the projects I’m involved with include somekind of “de-portalization strategy” (Thanks to Thomas Petersen of Hello Brand for learning me this fancy expression).
Do anyone have experience building widgets based on OpenSocial? Is this the way to do it? Example: If Wulffmorgenthaler were to build a lot of widgets should we use OpenSocial?
February 1st, 2008 at 4:38 am
On principle, you should definitely go for OpenSocial, it being open in nature. However, reality bites, and going OpenSocial appears to mean targetting only Orkut at this point?
And uh, who uses Orkut?
For now, you’d probably be better off building an app for Facebook, and then perhaps port it to OpenSocial at some point in the future, when more OpenSocial containers appear.
February 4th, 2008 at 2:40 am
“De-portalization” sounds like taking the old and adapting it to the new situation. But what is the new situation?
I like platforms like yourmini.com, these are widget platforms that let you build, trace and analyze their use.
On a high level, it’s very close to your Traceworks.
Because once you have a widget, you would like to promote it, analyze it and improve it. And this cycle will be the same for all widget owners.
Controlling this future flow of data is the objective of platforms like yourmini.com.
Needless to say that the one who will hold the most data on the most widgets will be a big winner.
…if he has access to the best algorithm to analyze them of course.
By the way, I’ll send you, the proposal you asked for, on wednesday.
Khalil