If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

Yes, you heard about Google Wave but you have not tried it yet. Well, for one, though you may already have it, you do not have any idea as to how you should use it or whether it could work to your advantage. Well, here is a list the advantages and disadvantages that you could use to help you decide whether it is already high time for you to use this new technology.

In order to better understand what Google Wave, you need to understand the rationale behind its creation. You need to know the answer why it was created in the first place. Well, basically, the technology was developed to give communication a more advanced form where almost all of the commonly used means of message exchange nowadays are collaborated into one system. However, the more important question that needs to be answered is, “What are its advantages and disadvantages?”

Feature Feedback Reasons
Interface Ok Its interface is impressive but at the same time it is not difficult to understand because it is similar to the interface used in emails, only that it has some additional elements. It also gives you a recap of how much changes the waves have undergone since the last time you went online, a new feature that a lot of applications and system would surely die to imitate.
Participant contribution Ok It encourages people to contribute to a wave that has already been posted.
Collaboration Ok You can actually see changes unfold before you at the same time your friends incorporate these changes. Google wave offers real-time collaboration in a new and more efficient way than others do.
Revisions and rollbacks Not okay You still need to do revisions manually.
Reply hiding Not okay Replies can be in any form and since Google Wave still does not allow reply hiding, an array of replies might look messy in one wave.
Invitation Not okay It is still limited so the purpose of creating the system has not been fully realized yet.
Update notifications Not okay You don’t get any notifications on waves that you intend to follow may it be in the form of chat, email, and the likes. So if there are a lot of waves flowing in, some would just get lost along the way.
Chat Not okay It is still very unreliable. It’s fast one moment and then slow and hen very slow and back again.
Stability Not okay The population of users affects the stability of the system. Thus, the more people using the technology, the most unstable it gets.
Google account requirement Not okay This is only a problem for customers and users who are not so savvy yet in using the Net.
Online users Not okay Its indication as to who is online is still not that reliable.
Mark-up editing Not okay Source code view is still not available.

Although there might still be some problems with Google Wave, it does not undermine the power it brings to users. And, people will just have to wait for improvements that could make this technology much, much better.

Although the business of web designing is a very thriving business, the relationship between the designer and clients usually lead to some strain especially when a project is about to be finished.

In most cases, the problem is caused by miscommunication where the customer expects to get a certain result and discusses what he thinks he wants. These information are then interpreted by the developer according to his own understanding, in accordance to how his interpretation was developed based on his own biases, and eventually get a result that is not always appreciated by the customers.

Most customers then would think that they did not get the service they intend to get. Some would even wonder why, amidst both parties having discussed what was needed to be done, the output was still unsatisfactory. On the side of the web designer, however, redoing the whole designing when it is about to be finished is not at all inspiring especially if the web designer also thinks that he has actually given what the customer said he wanted.

Another problem that designers and customers have aside from miscommunication is how they set priorities. For customers, they have their set of priorities that are related to what they want to achieve in their business. Often, these priorities are not that important in web designing and how websites should function in the online world. That is why, web designers also have their own set of priorities that, although may not coincide with what the customer wants, are all geared to make the website function effectively.

The best way to bridge the gap between customers and web designers is to assure effective communication that leaves all the but’s and gray areas away. This is another burden that web developers should carry because it is them that understand the process. The web developer should make sure that when he is developing a website for somebody’s online store, he should be able to explain to the customer everything that the customer should know through the use of details that the customer could understand. The web designer should also be able to show the customer what problems may arise if ever the wants of the customers are incorporated in the website. Aside from this, the web designer should be able to give customers a better alternative if what the customer wants is impossible or difficult to achieve. Lastly, it helps if you could be able to show the customer a prototype of the web designer that both of you have agreed. This will help you lessen your problems if ever the customer sees some things that may not be too interesting for his or her taste.