Timeline for Complex search window
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 14, 2012 at 15:22 | comment | added | user1757436 | There is [similar question] (ux.stackexchange.com/questions/28826/…) that might interest you. Searching and filtering the results on Cars.com is an example of the type of search you are describing. | |
| Nov 13, 2012 at 9:49 | comment | added | CyclingFreak | @greenforest This window will be for dealers, selling our products. When they open the window, basic search will be the first presented. It could be that the product manager can define some default options. Users with a basic understanding will only need the first level of functions, experts can tweak the search by requesting all functions. A questionnaire or wizard is not going to be the best because it is hard make it dynamic and needs more clicks when a quick selection is required. Of course, users will get a basic training. | |
| Nov 13, 2012 at 9:27 | comment | added | greenforest | Is this product for consumers? If not, popup and implicitly assuming users will know in what group they are (default, advanced, expert) sounds strange. You might better want to go with some sort of questionaire/wizard or with a default list and then allow for filtering. | |
| Nov 13, 2012 at 8:32 | comment | added | CyclingFreak | @JuanLanus Thank you for this input. I have modified the labels. And also thank you for the upvotes, I have added the images inline. | |
| Nov 13, 2012 at 8:31 | history | edited | CyclingFreak | CC BY-SA 3.0 |
added wireframes
|
| Nov 13, 2012 at 7:58 | comment | added | CyclingFreak | @Igor-G In the admin website, the product manager can define all the functions and options. He may choose between: text, number, boolean, checkboxes or radiobuttons. Also, he can define on which search level the function should appear: null, 1, 2 or 3. | |
| Nov 12, 2012 at 18:17 | comment | added | Juan Lanus | Slightly OT and a bit picky: In the first wireframe I'd use "less" instead of "back" as the opposite of "more", because "back" might make the user fear to be taken out of here to a previous context. In the second example I'd use "quick search" instead of "fast search". Hopefully all searchs will be fast while only some will be quick as in quick and dirty, i.e., easily started. Also, now you have 11 reputation! | |
| Nov 12, 2012 at 17:26 | answer | added | Igor-G | timeline score: 1 | |
| Nov 12, 2012 at 16:24 | comment | added | Igor-G | are you going to allow multiple selection? | |
| Nov 12, 2012 at 16:14 | comment | added | Jeroen | Drag unsuspecting people in front of a screen and watch which one gives the best result. | |
| Nov 12, 2012 at 9:59 | history | tweeted | twitter.com/#!/StackUX/status/267929708069519360 | ||
| Nov 12, 2012 at 8:56 | review | First posts | |||
| Nov 12, 2012 at 9:42 | |||||
| Nov 12, 2012 at 8:41 | history | asked | CyclingFreak | CC BY-SA 3.0 |