Is OpenSocial hurting portals?
Last week, I participated in a panel discussion on using OpenSocial in the enterprise, along with execs from IBM, Atlassian, and SocialText. Although only two of the companies represented had portal offerings, a good portion of the discussion was focused on portals, namely is OpenSocial destroying the portal world and portlets in general.
First, portals are evolving. I reflected in a previous post that “The nature of portals has changed, and with GateIn (eXo + JBoss), we’re seeing portal’s transformation from an aggregator of external applications to a platform for building and delivering services that add value to the user organisation.”
In this world, the question is not whether a developer has to choose between portlets or gadgets but rather, which services are best delivered as gadgets and which as portlets.
At eXo, we do not make a great distinction between a gadget or a portlet. They are merely categorized in a way that makes it easy for users to go and grab more gadgets or portlets to customize their application. The user doesn’t care.
Next generation portals will support both models but this is just one of the building blocks of the platform of tomorrow. Horizontal services like content, mail, calendaring, or profiles are other pieces that can be mashed up together to easily build a custom web application… online. We’re baking functionality into GateIn that will enable it to be the ultimate “mash up” platform for combining and recombining components. Times have changed, let’s be more agile.