Google wasn't kidding when it said it planned to bring Google Instant to every product, platform and even inside browsers as soon as possible. The latest Google Chrome dev builds already have a sort of Google Instant implementation, albeit not enabled by default.
If you run Chromium, Google Chrome Canary or the latest Google Chrome dev build with the "--enable-match-preview
" command-line switch you'll be able to access the early implementation.
Note that this isn't Google Instant included in Chrome, rather it's the implementation of the concept, Chrome Instant if you will. This has some obvious advantages, but also some major drawbacks.
As you start typing in the Omnibox, Chrome displays a preview of the first suggestion the browser provides. If it's a Google search, it loads the Google search page and shows the results for the query being typed.
Unfortunately, it doesn't use predictions, like Google Instant does, rather it just does a search for what you've managed to type. Hopefully, this will change by the time the feature makes its way into the browser enabled by default.
But the advantage of doing a native implementation is that Chrome Instant applies to more than just Google Searches. If what you're typing matches a page you visited before, Chrome previews that page.
Again, the implementation is not ideal. If Chrome just loads a new page for each new suggestion, you get a flurry of activity that proves much more distracting than Google Instant.
What's more, it may load some pages that you might not want to be seen viewing at work, for example, but which may be in your history even if it's not the page you actually wanted.
Still, this is just an early implementation and Google will probably address all of the shortcomings before releasing the feature. While Google Instant may have been well received, it's not an universal solution and has to be adjusted for each particular application. Hopefully, Google will take this into consideration. [via Google OS