One of the most visible effects of choosing either web or desktop technology is the way the resulting application will appear. Right now there are a couple of development frameworks to take into consideration. These are in no particular order:
- Basic web application
- Netbeans/Eclipse Rich Client
- Swing/SWT application
(This list is Java oriented.)
All of these have advantages and disadvantages. The list above can be divided into two main categories. To no surprise these are Web and Desktop. Anyway, right now I’m working for my employer on a document which ellaborates on these differences. Also I’ve submitted a proposal to the NL-JUG’s upcomming J-Fall to do a talk about this subject for my employer. I hope they’ll agree with me that it’s an important subject to reflect on a bit.
Finally you’ve finished your latest wonder. Now to boldly move on to marvellous new functionality.
Wait a second.
Before moving on to something else it would be nice of you to actually make your app available to your users.
Continue reading “Rich Client vs. Web 2.0 – Deployment and maintenance”
In my opinion a lot of companies are going to make decisions in the near future about using Web 2.0 or Rich Client for their next end-user applications. Both have their respective strong and weak points.
Over the next couple of weeks I intend to put up some postings about my opinion on various aspects of Web 2.0 compared to Rich Client development. Since I myself am mostly involved with Java software development I will focus on the aspects of frameworks and platforms based on the Java language.
For this intro, let’s lay down some basics by defining what Web 2.0 and Rich Client is.
I’ve found a nice definition of Web 2.0 at O’Reilly Radar:
Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the intrinsic advantages of that platform: delivering software as a continually-updated service that gets better the more people use it, consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating network effects through an “architecture of participation,” and going beyond the page metaphor of Web 1.0 to deliver rich user experiences.
Now on to Rich Client. There is a very good definition available at TechTarget.com:
A rich client is a networked computer that has some resources installed locally but also depends on other resources distributed over the network. The rich client’s configuration is somewhere between that of a thin client, which relies largely upon network-distributed resources, and a fat client which has most resources installed locally.