Archive for SAAS

Segmenting web platforms

Web as a platform is an interesting topic for most people in the software industry. Marc Andreessen (Ning) recently made an attempt to classify this platform in his post The three kinds of platforms you meet on the Internet. In the follow up analysis posted by Josh on ReadWriteWeb Platforms on the Web are Platforms on a Platform, this classification and value of different platform levels is questioned. Before I state my views on this, let me capture Mark’s classification in a summary below:

L1 platform. Loosely coupled REST/SOAP based API integration. Example: Flickr API.

L2 platform. More deeper integration of developer’s application injecting into the platform UI. Example: Facebook API.

L3 platform. A runtime that hosts developer code. Example: Ning.

Marc’s argument that L3 platform are the best, is certainly questionable and Josh makes points in this line. While a scalable web platform with Social Networking API is a powerful one, expecting others to bring their users and user data to your hosted platform is not in the best interest of the company/group that wants to add those features to an existing site/application.

A better solution could be a add-on social networking platform with API which the company/group can co-host and integrate. They get to keep their users and user data and can achieve better integration.

This is like a “Web 2.0 Application Server” as shown in the picture below. Deployed alongside the current Web 1.0 website and can provide social networking features overlayed on top of it.


Would this be more acceptable to those currently on using web as a Web1.0 platform and would like to add social networking among their users (use web as a Web2.0 platform)?
Technorati Tags: , , ,


Comments (1)

My interview at

Rajesh Setty has published my interview with him Behind the scenes – Dekoh; Interview with Vijay Pullur. I have talked about several topics like our history, why Dekoh?, how is it different from Adobe Apollo and Google gears, enterprise and SaaS ISV use cases for Dekoh etc. Thanks Rajesh for interviewing me and publishing it.

Comments (1)

Bringing the best of Desktop and Web together

The main idea of Dekoh is to bring the best of features on Desktop and Web to end users and developers. Jay in his presentation had a nice slide that captures this.

Best of Desktop and Web

Here is a brief description:

Universal Data: Applications can blend data on their file system with data on the web (website APIs) in their applications.

Control over sharing: While desktop is a fully private environment, the concept of social web is community based sharing. Dekoh desktop applications can be shared thru Dekoh Network. It is your private network.

Benefits of a hosted application: Desktop applications are self contained and rich in user interface (also easy to install and manage). Deploying and managing web applications is a little geeky job (folks in enterprise software world know this, the reason why SaaS model is becoming popular). Dekoh camouflages all the complexity. Installing and running Dekoh desktop and applications is just a one-click operation. It is totally end consumer usable.

Bringing web 2.0 to desktop: Use your personal media (photos, music, video, blogs, books….) and collaborate with your personal network. Run your web applications on the desktop

Developer friendly: Dekoh is based on open standards and is an open source platform. Developers with wide ranging skills like HTML, CSS, Javascript, Flash, Java, JSP/Servlet, PHP, .Net can write applications on their desktop and share it over the web securely (Read FAQ). More exited? participate in Dekoh development by joining the Dekoh community

End user applications: End consumers can install Dekoh Applications and organize their personal media and share it with their personal network.

Technorati Tags: , , ,

Comments (6)