> Any thoughts regarding how to put a no click interface to use? There was one aspect of the no-click interface that worked for me: the timed trigger button. As you hover over the button, it "fills" itself with a darker color like a progress bar and then triggers when the progress reaches the full point. It gives you a little bit of a "comfort delay" instead of the BAM! BAM! BAM! of the rest of the experience (the first BAM! made me jump out of my seat... not fun.).
So I guess it seems to me that a slower, more fluid approach might make more sense, in which the interface slowly reveals something about what is going to happen if you move to a particular region, but allows you time to move out in case you didn't really want to do that. I move my mouse cursor around to random spots on the screen so I could imagine myself accidentally moving to or hovering over a region that enacted something that I really didn't want to do. It brings up some good questions, however. evan k. stone | ux | dragnet solutions, inc. ________________________________________________________________ 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
