Podio is a new cloud based business tool, it is sort of the Facebook for business. It is also clearly a direct competitor to SalesForce.com and LotusLive in my opinion. It looks like it has a really nice set of applications right out of the gate and they are tailored for running a business. It has things like email, calendar, meetings, project planning, crm, and all kinds of tools for different industries.
I have been digging into the various “cloud” offerings on the net and trying to see if there is a common ground in this space and as usual it appears the usual players are making bets on their “cloud” offerings. When you start seeing sites like SalesForce.com, LinkedIn, Facebook, or API’s like Microsofts Azure, all using different technologies to provide applications within “their cloud” it quickly shows people are off in their own camps. I have been reading up on the DeltaCloud (Many clouds. One API. No problem) which is attempting to solve this disparity with a wrapper approach. As long as you have a particular clouds “module” installed on the server, your code can connect to and participate in that cloud. The API’s seem to be very basic out of the gate but I think the direction is worth watching. Amazon has a huge web presence and companies like Eucalyptus have even standardized on its API’s for their own back-end so it makes me wonder if there will be camps but not many camps in the end.
Using the same application programming interfaces (APIs) that Amazon deploys for its Amazon Web Services (AWS), Eucalyptus allows users to set up their own private clouds and move workloads among internal servers, or to and from AWS. The software is available both as free, open-source code and as a paid version. – PC World
Do we need the same for collaboration? Open Social (Many sites, one API – sound familiar?) is suppose to fix that but it isn’t totally adopted by all players either.
A common API means you have less to learn to build for multiple websites. OpenSocial is currently being developed by a broad set of members of the web community. The ultimate goal is for any social website to be able to implement the API and host 3rd party social applications. – OpenSocial
If we really want a true cloud then there is going to have to be some level of common API, data model, and interfaces across the players otherwise developers and IT will be needed for the integration points. As more and more stuff moves to the cloud you may see more and more job openings for “SalesForce.com developer” or “OpenSocial developer” or “AWS experience a plus”.
I think this is a frontier of opportunity for any IT person or developer – which is one of the reasons I love this industry. It is forever changing and challenging.
I was actually researching the OpenSocial specification and did a Google search on what sites use OpenSocial. To no surprise, there are clearly two camps here – Facebook and OpenSocial. With the announcement of MS Office for Facebook you can clearly see the two camps that have been formed. Check out an interesting slide presentation from Jawad Shuaib – yes it was posted quite some time ago but I think it is still somewhat relevant (you can also see it below). One small point is that SalesForce.com supports OpenSocial and it is arguably an extremely successful product. With the introduction of VMWare integrated with SalesForce.com services (vmforce.com) the development platform potential is amazing. Check out the article written by Bernd Harzog where he outlines some of the speculations of what this will actually be. A key attractive point from one developer (me) is this:
“Then how about if developers of Force.com applications are given the option of building these apps in the traditional SalesForce.com tools, or also via Spring, Groovy, and Grails (the SpringSource development tools). This would in the long term get SalesForce.com out of the developer tool business, which it probably does not want to spend money on in any case.”
I figured I would play around with the Google Friend Connect stuff. I added it to this site (see the right side panel under Planet Lotus). You can join my site and also comment using your Friend Connect id. This id can then be used across all of your sites you “subscribe” to. As I play I might add more features – since there seems like a lot of things you can do with this.
With the announcement of Google Wave, we now have three distinct camps (maybe more) for creating that new Web 2.0 killer application/component. We have a lot of consumers of widgets (check out the supported sites) but we have three main API “frameworks”; Microsofts Silverlight, Apache Shindig and now Google Wave. Shindig and Wave are very similar in the roots (support the same base specifications) and are very compatible at many levels. There are clear distinction is in the API’s that both platforms support (Wave actually extends OpenSocial) but with the added extensions Wave supports it looks like it has gone a little further in supporting broader real world use cases (Robots, Embedded API). The great thing about Wave is it does support OpenSocial gadgets and its specification:
“Gadgets, which you may know from OpenSocial, are client-side programs that make it easy to write full applications inside of Google Wave. The neat part is that we’ve introduced an extension to the OpenSocial gadgets API that enables you to take advantage of the collaborative nature of Wave when building a gadget.” – link
Silverlight continues to be very MS like but seems to be gaining a lot of ground – I am seeing more and more job openings for Silverlight developers. Silverlight also supports OpenSocial gadgets and compliments Silverlight very well.
So if you want to start developing base gadgets for these platforms and sites, stick with Open Social gadgets – and since OS Gadgets just require an iFrame you can stick them pretty much in any web page. You can start developing and debugging these gadgets with the Open Social Development Environment (OSDE) for Eclipse today. You can even watch the introduction video that walks you through what OSDE can do.