Note to developers,advantages and disadvantages of web2.0 and caution
August 12, 2009
There are certain factors that developers need to consider while designing Web2.0 applications. Some of them are:
1) The developer must be well aware of the application interface because of asynchronous communication between the client and server in Web2.0 applications as opposed to page-refresh in Web1.0 applications. So they should consider new ways to notify the users about the ongoing internal processing at the server side for which page-refresh was meant in the case of Web1.0 applications. This can be done by displaying a simple message in a <div> element rather than using alert boxes. By doing so, the user need not stop processing in order to respond.
2) After data is provided to the interface, users should be able to identify what is new. For this purpose some distinct color can be used to highlight the data.
3) Developers must take care that the form is not submitted to the server even if the user clicks the button inadvertently before entering valid data. For this purpose, the button should be enabled only after valid data entry. Hence interface elements should be enabled and disabled appropriately by the developer.
Advantages of Web2.0 architecture:
1) Asynchronous communication: Each time an event is triggered, the user does not have to wait for a response from the server.
2) There has been an increase in the number of tools used for creating Web2.0 applications.
3) A rich online user-experience is afforded by techniques like AJAX.
Disadvantages of Web2.0 architecture:
A higher degree of programming skill is required on the part of developers.
Caution in using Web2.0:
The upcoming of Web2.0 technology does not mean traditional or Web1.0 applications have become obsolete. It is also not necessary that web applications henceforth be developed only by using the features of the new technology. For instance, shopping cart applications which are usually employed by online e-commerce businesses may be developed using Web1.0 approach as they provide just the catalogue of products to the buyer and do not need to promote any interactivity.
With the emergence of new tools for developing Web2.0 applications, developers should not rework all the interface elements with the aim of providing a rich user interface because users may find it hard to work with applications composed of unfamiliar widgets. Hence it is better to retain the traditional interface elements with which they are familiar.