Speaking anecdotally, I would say I come back to the images results page about 90% of the time.
Some of the ways I use Google Images is when looking for a company logo for a presentation, album artwork for my MP3 library, book art for my Delicious Library database, etc. In all of those cases, I often go to a search result and discover that the image, once viewed full size, does not meet my needs, and I need to return to the search results in the same place that I left. On Mon, Dec 7, 2009 at 3:19 PM, live <[email protected]> wrote: > Come back? > Honestly, have you ever had a need to go back to images after you've > google/binged them? > Can you imagine a use case scenario? > > > > On Dec 7, 2009, at 12:04 PM, Jayson Elliot wrote: > >> I would caution STRONGLY against the "bottomless scroll," however. >> Bing.com >> has been using it in their image search, presumably as one way to >> differentiate themselves from Google. >> >> It's been a usability disaster. >> >> The page draws dynamically, making it difficult for a user to develop any >> spatial memory of the images they have found. As the user scrolls, they >> encounter a behavior they were not expecting from a scroll bar, and the >> ability to intuitively understand where one is in the results set is >> removed >> by the lack of location cues. >> >> Once a user leaves the page, they cannot return to their selection on the >> page via use of the back button. If they scrolled through several "pages" >> of >> images, they will come back to find themselves looking at different images >> than when they left (after waiting several seconds for the page to >> redraw). >> > > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
