Comments for Why We Need Web Apps on the Desktop

Etelos Goes Offline with MediaWiki, WordPress and the Apps You Build

2008-04-21T10:02:24Z

The Etelos Application Framework today launched a key new feature: the ability for applications there to run offline and sync when connectivity is available. The company requires zero code changes to be made in order for apps to go offline.

From apps developed natively for the Etelos marketplace to enterprise installs of Google Apps, MediaWiki and WordPress - the company expects a wide range of apps to make use of the offline functionality.

]]> From Google Gears to (in theory) Firefox 3 to the mysterious Yahoo BrowserPlus project - a lot of people are clearly trying to make apps usable offline. We've debated the soundness of that trend here at RWW, but we do love us some desktop RSS reading, too.

The Etelos offering is just the latest from a company that offers primarily enterprise app developers a wide range of services. The idea behind Etelos is that the company takes care of everything from billing to customer management, allowing developers to make and sell great apps. Now those apps will be able to live offline, one more good reason to offer apps through the platform.

App account administrators (on the customer side) will be able to set varying permission levels to determine which users can access what information for syncing offline.

For the immediate future, at least, when in-flight wifi still seems a ways off and connectivity in general isn't what it ought to be - this sounds like a good idea. Offline access and later syncing is something that sounds uninspiring in theory but is very exciting when you're using it. Google Gears offers another level of emotional experience when you get to feel disappointment over the shaky quality of syncing once back online. There's certainly room for competition in the world of offline access to web apps.

Comment from Robert Q Benedict on 2008-04-21

2008-04-21T11:55:09Z

What might be the ceiling on how complex the applications might be? It sounds great, but also sounds like something that could require more user user support? We now have to field desktop issues as well as web? Any thoughts?

Comment from Ajay on 2008-04-21

2008-04-21T12:41:18Z

good work
not much bandwidth is reqire.
i will definatly use it in my blog
http://readerszone.com

Comment from Marshall Kirkpatrick on 2008-04-21

2008-04-21T14:40:29Z

Robert, those are good questions for sure. Perhaps some one from ETelos will reply here in comments.

Comment from Ahmad Baitalmal on 2008-04-21

2008-04-21T15:25:56Z

Robert,

I'm not sure exactly how to quantify the complexity you have in mind, however, the general rule is if its a LAMP compatible application it should run with no code changes at all. We use SugarCRM as an example because it is a rich application with many typical features that users have come to expect. The platform is open to the developer to add as much complexity as they would need on their online server.

As with any software product, user support is expected. Many of the components AOP relies on are very well community-supported already and that was a big part of our decision to stick with solid components that are well understood and relied upon. With that mentioned, an application provider would still provide the same support they would provide for their online server application. AOP makes it so they can support both interfaces with the same code base.

The developer can concentrate on building and maintaining an excellent user experience with their application in a server environment, AOP replicates that same exact environment on the user's desktop.

Comment from Marcin Grodzicki on 2008-04-21

2008-04-21T16:17:30Z

The world just keeps coming back in circles :) Current offline apps are a bit shaky indeed: RTM, Docs - the only 2 I use mostly don't work (on a mac at least). I don't really get where the problem is - the browser, the Gears? Still plenty of space for innovation here, but I don't think that more than 2 - 3 can actually survive competition.

btw. I'm gettin the "Script not responding" message whenever I load RWW today.

Comment from daniel on 2008-04-24

2008-04-24T10:38:56Z

according to crmbuyer http://www.crmbuyer.com/rsstory/62681.html?welcome=1209032918, etelos have 3 patents pending:

- one that enables browser-based applications to function offline;
- another that reconciles changes made while offline,
- and a third that synchronizes data with any other AOP-enabled application when returning to the cloud.

that means that etelos basically claims the whole offline technology. Interestingly this is not mentioned in your article.

dany