ContentsConclusionsWeb applications have strengths and weaknesses

Previous: Conclusions | Next: The Internet is here to stay

This probably doesn't need to be pointed out, but there are some disadvantages to writing web applications. They are typically more difficult to write, test, and debug. They are also necessarily more complex because everything doesn't get compiled to a single executable.

Web applications don't have the same look and feel as fat client applications. You'll never find them on the shelf of a local software store. They are different than what Microsoft and it's buddies sell. Period.

To offset these disadvantages, there are tremendous benefits of web applications during their use. They can be accessed by users all over the Internet or intranet. They are much easier to maintain and redeploy. They concentrate the "heavy lifting" onto server machines where they can be tended by system administrators (either centrally or via network). They are much easier to scale as demand varies and availability of server hardware fluctuates.

Not every application should be on the web. Some specific examples are:

• spreadsheets
• graphic presentations
• multimedia development
• certain types of personal information management
• single-player games

The decision about whether your application should live on the web or be a traditional fat client needs to be decided very early. There are certain user interface limitations that some developers don't want to live with because they can't imagine how to do their work without some GUI widgets. These considerations need to be weighed against the realities of what the end users need.

ContentsConclusionsWeb applications have strengths and weaknesses

Previous: Conclusions | Next: The Internet is here to stay