Desktop versus Web Applications and Ongoing Function Gap (Are Rich Internet Applications really rich?)

As we started to search architecture for our ERP platform in 2001, there were 2 options to select in Java:
1- Desktop-Based Applications:
If we select this option, 2 other ways to select; one is using AWT or Swing, the other way is building-buying a new component presentation framework. As my previous development experience Desktop Java was extremely difficult. Applications written in Java was not responsive as native windows applications. AWT and Swing was very heavy. Building a new presentation framework was another unknown way to go since requires many UI engineering effort(Layout-Window Management, Rendering, State Management, Event Model, Release Management, Server Communication etc.).

2- Web-Based Applications:
Here we had another options; first is pure HTML and browser-based option, second is using Java in browsers (ie. Applets). Some ERP vendors, uses another option that's clients are web-based but doesn't require (or minimal setup) setup and loads applications on demand. Oracle ERP uses this model, its loader is JInitiator. Sun had offered similar function with its JNLP and Web Start technology.

What we selected is first option of Web-Based Applications; 100% web-based solution.

For the rest of post:
http://fromapitosolution.blogspot.com/2008/10/desktop-versus-web-applications-and.html>