I think a 100% "no click" interface has no interest, although there are some actions that don't need a click... In the intranet project I mentioned yesterday (in which I planed to implement such an UI approach), users could browse (very quickly) through various topics indexes just by moving the mouse over screen areas; but when they decided to go to 1 specific web page, then they had to click.
Someone mentioned the slowness of the Flash example; indeed speed of display of content is a necessity in reaction to mousemoves., because mouse moves are fast by nature (faster than pointing & clicking). Furthermore, some elegant graphic movements can be associated to a mouse move (the icon dock on OSX fo instance), which IMHO look less "natural" when a click is required... JB > Jon- > > Monday, July 11, 2005, 4:37:32 AM, you wrote: > > J> I enjoyed taking a look at this new [?!?] UI, but the proof of the > J> pudding, for me, was when I accidentally moved the mouse across the > J> answer to a question, and it assumed I had "answered" (with no way to > J> "back up"). I'd say I would have to pass on this one. > > That was pretty much my take on this as well. I had fun exploring with > the clickless approach but had trouble navigating with it. I think I'd > agree with Scott that it would be useful to show users what's > available but that click is important to keep them out of trouble. > _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
