Sunday, 5 February 2012

Google Instant: An Insight Into Its Practicality

Google Instant shows search results as searchers type their search terms. They need not to finish typing the full search terms either. Google will be bringing right contents, rather say predicted searches, in response to the search inputs. Searching for anything on Google becomes faster, instantaneous, smarter and, of course, interactive in nature with this innovation and change at Google. This mechanism of Google supports multiple updated versions of almost all browsers. Users find turning on and turning off the icon of Google Instant easy by using the gear icon on the Google.com.

However, users of Google Instant are to welcome cookies on their browsers. It is like a situation when people are either to "like it or lump it!" If users wish to enjoy the benefits of the Google Instant, they must have to enable cookies on their browsers. Cookies are popular for creating many kinds of mischiefs to the portals. This is the reason why users of this mechanism consider it to be a kind of 'infliction' while opting for using it. This idea seems to have no practical value also as this may choke off the web bandwidth with useless junks.

All the same, users need not to be harshly critical about this novel idea as well. Search experiences on Google will remind the users that prior to the days of the introduction of this mechanism, users would generally devote longer times to find out the search results and there have not been simultaneous predictions about their searches also, which help searchers to identify their exact search faster and flawlessly. With using this mechanism, users can cut down their search period which is deemed to be very vital for the progress of an organization, as well as of an individual.

Google has said that this mechanism is faster, smarter and instantaneous. It is found to be interactive too. Users have rightly pointed out to a fact that it creates a similar interactive situation as Ajax web pages generally create. Ajax, which is the acronym of Asynchronous JavaScript and XML, allows web pages to interact with their users as they keep typing. Similar sort of picture can be seen here too when Google Instant starts suggesting or predicting search results to the users as soon as they begin typing their queries and also modifies its predictions or suggestions with each new letter they type.

In a word, the objective of introducing this innovative mechanism by the Google engineers is very simple and clear: to save time. But, the question of million dollar worth is that whether it will really be able to save time. Google has come up with an estimate where it has shown through a calculation that this innovative mechanism can save users globally from wasting their 3.5 billion seconds a day, as a whole. This is no doubt a rattling idea about saving their precious times.

There is also a group of netizens who counter the views of the giant search engine on its new algorithm. They argue saying that whether Google Instant actually saves time or not for users personally will depend on what sort of users they are. They put forward a valid logic to the effect by saying that this mechanism may also slow down and distract almost all users. They say since the individual users theoretically save seconds on their individual searches, it is not at all well-defined or understood that users will welcome Google Instant as a time-saver for them, even if it actually is.

However, before Ajax infusion into the Google search mechanism, it would deliver the same results. There will be millions of web users who will find it to be innovative and entertaining. There will also be more or less numbers of web users who will find it to be not up-to-the-mark. But, without real-time search result, Google Instant has less or no practical necessity.

Users of Google Instant find the idea to allow cookies to be annoying. However, search time reduction and simultaneous search predictions are of great value to the users who work on search engine optimization, in particular.


View the original article here

No comments:

Post a Comment