3 ms·
If you can anticipate a user's search needs, why not take the next step and provide the answers before the user gets around to searching?
by anamax 17y ago
If you can anticipate a user's search needs, why not take the next step and provide the answers before the user gets around to searching?
- sundeep 17y agoOne step at a time :) What you suggest would benefit from the performance/feedback from what the OP suggests. This is basically what I am interested on working on currently , using "clues" gleaned from what the user is doing (a la RescueTime) to reorganize/reformulate a user's search query.
- shorbaji 17y agoFirst reason is to minimize error rather compound it. Second reason is to avoid overloading the user with information. I do expect that the set of queries prepared for a user will be large and possibly imperfectly ranked, at least initially. To use this set in its raw form to pre-fetch answers will dilute accuracy and be a large amount of information. Rather, I take the approach that search is a commodity that is already fast enough and good enough. I let the user choose (and thereby rate/vote up) a query and then fetch only relevant results.