2 improved punctuation, and formatting
source | link

An alternative is live/continuous search - update: Update the search results immediately on every button press. In addition to improved efficiency, it can also help to solve such usability problems as users typing more search parameters than are needed, users not noticing the find button, users making a typing mistake and not knowing why the search results were empty etc. [Lauesen05 page 286].1

Of course, technically a continuous search is more complex to implement than a simple search form. In web environment, Ajax/Comet is needed, and also the server-side search must be fast. But the implementation complexity is easily justified with improved usability, if the search is a central feature.

Whatever you do, it's always a good idea to make a usability test to find out whether the users will know how to use the system, and then make improvements as necessary.

[Lauesen05]1 Soren Lauesen, User Interface Design: A Software Engineering PerspectiveUser Interface Design: A Software Engineering Perspective, 20052005; page 286

An alternative is live/continuous search - update the search results immediately on every button press. In addition to improved efficiency, it can also help to solve such usability problems as users typing more search parameters than are needed, users not noticing the find button, users making a typing mistake and not knowing why the search results were empty etc. [Lauesen05 page 286].

Of course technically a continuous search is more complex to implement than a simple search form. In web environment Ajax/Comet is needed and also the server-side search must be fast. But the implementation complexity is easily justified with improved usability, if the search is a central feature.

Whatever you do, it's always a good idea to make a usability test to find out whether the users will know how to use the system, and then make improvements as necessary.

[Lauesen05] Soren Lauesen, User Interface Design: A Software Engineering Perspective, 2005

An alternative is live/continuous search: Update the search results immediately on every button press. In addition to improved efficiency, it can also help to solve such usability problems as users typing more search parameters than are needed, users not noticing the find button, users making a typing mistake and not knowing why the search results were empty etc. 1

Of course, technically a continuous search is more complex to implement than a simple search form. In web environment, Ajax/Comet is needed, and also the server-side search must be fast. But the implementation complexity is easily justified with improved usability, if the search is a central feature.

Whatever you do, it's always a good idea to make a usability test to find out whether the users will know how to use the system, and then make improvements as necessary.

1 Soren Lauesen, User Interface Design: A Software Engineering Perspective, 2005; page 286

1
source | link

An alternative is live/continuous search - update the search results immediately on every button press. In addition to improved efficiency, it can also help to solve such usability problems as users typing more search parameters than are needed, users not noticing the find button, users making a typing mistake and not knowing why the search results were empty etc. [Lauesen05 page 286].

Of course technically a continuous search is more complex to implement than a simple search form. In web environment Ajax/Comet is needed and also the server-side search must be fast. But the implementation complexity is easily justified with improved usability, if the search is a central feature.

Whatever you do, it's always a good idea to make a usability test to find out whether the users will know how to use the system, and then make improvements as necessary.

[Lauesen05] Soren Lauesen, User Interface Design: A Software Engineering Perspective, 2005