Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

They tested that:

For example, we tried a prototype where we waited for someone to stop typing before showing results, which did not work. We realized the experience needed to be fast to work well.



Is that what amichail is asking? It sounds like he's wondering why they don't just show the results updating with every letter you type, while not even bothering to show the dropdown predictive list of queries you may be typing.


Cursor down + return is pretty fast.


It’s never fast enough until people can’t tell the difference. “Pretty fast” is meaningless in that context. What matters is whether it is perceptibly faster or slower.


I think the real issue is something that Google is not telling us.

Maybe most people can't figure out they can press cursor down + return.

Or maybe this is a flashy way to distinguish their product from the competition.

Or maybe this is a way to encourage users to use shorter queries (as they can see how effective they are from the search results), thus forcing advertisers to pay more for more general terms.


I vote “people can't figure out they can press cursor down + return.” And that’s a perfectly good reason for changing the UI.


Even those who can figure it out probably benefit from fewer necessary steps, allowing them to pay less attention to the process of searching and more attention to the content.


I actually like Google Instant a lot. If I don't know exactly what I'm looking for - lets say I'm looking up some obscure HRESULT error handling thing, which I was - I can basically play with my query in real-time. It makes it much faster to do this kind of digging.


It's kind of like a REPL for your search queries. Kinda.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: