<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Mouse-over menus done right</title> <atom:link href="http://www.90percentofeverything.com/2007/02/13/mouse-over-menus-done-right/feed/" rel="self" type="application/rss+xml" /><link>http://www.90percentofeverything.com/2007/02/13/mouse-over-menus-done-right/</link> <description>User Experience Design &#38; Research, written by Harry Brignull</description> <lastBuildDate>Wed, 01 Feb 2012 11:09:19 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Harry Brignull</title><link>http://www.90percentofeverything.com/2007/02/13/mouse-over-menus-done-right/comment-page-1/#comment-982</link> <dc:creator>Harry Brignull</dc:creator> <pubDate>Wed, 14 Feb 2007 08:33:45 +0000</pubDate> <guid
isPermaLink="false">http://www.90percentofeverything.com/2007/02/13/mouse-over-menus-done-right/#comment-982</guid> <description>Hi Erik,
thanks for stopping by and posting your comments.
I understand that SPA is not meant to be a fixed element on a single page. I think this is basically why I have an issue with it - this style of mouse-over interaction is very prominent and can be overwhelming.
Pardon my metaphor, but mouse-over interaction is a bit like sesame oil. If you use the appropriate measure in the appropriate dish, it&#039;s a wonderful improvement. But if you add it slap dash to everything you cook, it quickly becomes your least favourite flavour.
It&#039;s clear that some people do like SPA, and some people really don&#039;t like it. So, to me it seems like that its more appropriate to offer on a per-user basis than a per-site basis. A Firefox / IE plug-in would allow people who want it to opt-in. The current model is that the people who don&#039;t want it need to opt-out - and since opting out involves adding a cookie, they have to remember to do this again every time they erase your cookies.</description> <content:encoded><![CDATA[<p>Hi Erik,</p><p>thanks for stopping by and posting your comments.</p><p>I understand that SPA is not meant to be a fixed element on a single page. I think this is basically why I have an issue with it &#8211; this style of mouse-over interaction is very prominent and can be overwhelming.</p><p>Pardon my metaphor, but mouse-over interaction is a bit like sesame oil. If you use the appropriate measure in the appropriate dish, it&#8217;s a wonderful improvement. But if you add it slap dash to everything you cook, it quickly becomes your least favourite flavour.</p><p>It&#8217;s clear that some people do like SPA, and some people really don&#8217;t like it. So, to me it seems like that its more appropriate to offer on a per-user basis than a per-site basis. A Firefox / IE plug-in would allow people who want it to opt-in. The current model is that the people who don&#8217;t want it need to opt-out &#8211; and since opting out involves adding a cookie, they have to remember to do this again every time they erase your cookies.</p> ]]></content:encoded> </item> <item><title>By: Erik Wingren</title><link>http://www.90percentofeverything.com/2007/02/13/mouse-over-menus-done-right/comment-page-1/#comment-972</link> <dc:creator>Erik Wingren</dc:creator> <pubDate>Tue, 13 Feb 2007 19:36:08 +0000</pubDate> <guid
isPermaLink="false">http://www.90percentofeverything.com/2007/02/13/mouse-over-menus-done-right/#comment-972</guid> <description>&lt;b&gt;Harry,&lt;/b&gt;
My name is Erik Wingren and I head up UX Research for Snap — the company behind the Snap Preview Anywhere (SPA) web service.
First I want to express my genuine appreciation of you sharing your experience with SPA and analysis thereof. This is how we learn and develop.
While I agree with the basic premise of your analysis of the SPA interaction, I have to state that I  think the meaning you attach to your third point — &quot;context of use&quot; — is either unfortunate or unfitting. Please don&#039;t get me wrong — context of use *always* matters — but IMHO the true importance and meaning of that point is lost when you compare SPA to *fixed navigational UI elements*.
Snap Preview Anywhere is not designed to be a fixed element on a single page. On the contrary it is designed as a distributed web service that enables site owners to enhance hyperlinks on their pages with preview functionality.
Again, I agree with the basic premise of your analysis. In fact, I recently posted an article on our blog where I reiterate Snap’s design objectives, acknowledge and respond to key points in the recent criticism and outline usability enhancements, aimed at solving the issues you raise and then some: &lt;a href=&quot;http://blog.snap.com/2007/02/09/spa-use-case/&quot; rel=&quot;nofollow&quot;&gt;The Snap Preview Anywhere Use Case&lt;/a&gt;
Cheers.
--
Erik Wingren
Snap UX Research
erik[at]snap[dot]com</description> <content:encoded><![CDATA[<p><b>Harry,</b></p><p>My name is Erik Wingren and I head up UX Research for Snap — the company behind the Snap Preview Anywhere (SPA) web service.</p><p>First I want to express my genuine appreciation of you sharing your experience with SPA and analysis thereof. This is how we learn and develop.</p><p>While I agree with the basic premise of your analysis of the SPA interaction, I have to state that I  think the meaning you attach to your third point — &#8220;context of use&#8221; — is either unfortunate or unfitting. Please don&#8217;t get me wrong — context of use *always* matters — but IMHO the true importance and meaning of that point is lost when you compare SPA to *fixed navigational UI elements*.</p><p>Snap Preview Anywhere is not designed to be a fixed element on a single page. On the contrary it is designed as a distributed web service that enables site owners to enhance hyperlinks on their pages with preview functionality.</p><p>Again, I agree with the basic premise of your analysis. In fact, I recently posted an article on our blog where I reiterate Snap’s design objectives, acknowledge and respond to key points in the recent criticism and outline usability enhancements, aimed at solving the issues you raise and then some: <a
href="http://blog.snap.com/2007/02/09/spa-use-case/" rel="nofollow">The Snap Preview Anywhere Use Case</a></p><p>Cheers.<br
/> &#8211;<br
/> Erik Wingren<br
/> Snap UX Research<br
/> erik[at]snap[dot]com</p> ]]></content:encoded> </item> </channel> </rss>
